This page contains frequently asked questions related to import:
On this page:
Importing Joint Coordinates in CVS or TXT Format
Expanded Question: I would like to import a .csv or .txt points file into SAP - one of the points represents the start point of a member, the next represents the end point. What is the best way to do this? I cannot find an import command that allows the importing of a plain comma delimited text file. The file is generated from another program and I would like to analyze structure with SAP.
Answer: The best approach to import the joints coordinates would be to use Interactive database editing in combination with Excel spreadsheet. The steps involved are outlined below:
- Create new model.
- Go to "Edit > Interactive Database Editing" and check "Expose All Input Tables" on the right side of the form.
- Now select table "Joint Coordinates" located in "MODEL DEFINITION > Connectivity Data > Joint Coordinates > Table: Joint Coordinates"
- Click OK, this will open "Interactive Database Editing - Joint Coordinates" form. Click "To Excel" button on the right side of the form.
- Cut and paste the content of the CVS or TXT file into Excel and place the data into their corresponding columns.
- Return back to the "Interactive Database Editing - Joint Coordinates" form and click "From Excel" button. This will transfer the data from the Excel spreadsheet to the SAP2000 form.
- Click "Apply to Model" and "Done" buttons to update the SAP2000 model.
Can I open my file in a lower version of the program?
While the input files are not backwards compatible due to the changes that may be introduced to the database tables in higher versions of the program, you may be able to use the following manipulation to import your model to a lower version of the program:
- Export your file as S2K text file.
- Modify the version of the file, say from 12.0.2 to 12.0.0, in the Program Control table.
- Open the lower version of the program and import the text file created in the previous step.
This approach should generally work if the two versions are "close enough" to each other, unless there was a change of database schema that directly affects the data stored in the file.
In any case, it is always good idea to check the import log for any warning and error messages. I would also recommend to carefully review the model once imported to the lower version.