table and field name over writes xml file

8/3/2019 Table and Field Name Over Writes XML File

1/6

ISO GEN041709M3 Rev. 0Berkeley, California, USA April 2009

Table and Field Name

Overwrites XML FileFor SAP2000

, ETABS

, and SAFE

TM


2/6

Copyright

Copyright Computers and Structures, Inc., 1978-2009All rights reserved.

The CSI Logo

, SAP2000

, ETABS, SAFE

are registered trademarks of

Computers and Structures, Inc. and Watch & LearnTM is a trademark of

Computers and Structures, Inc.

The computer programs SAP2000, ETABS, and SAFE and all associated

documentation are proprietary and copyrighted products. Worldwide rights of

ownership rest with Computers and Structures, Inc. Unlicensed use of these

programs or reproduction of documentation in any form, without prior writtenauthorization from Computers and Structures, Inc., is explicitly prohibited.

No part of this publication may be reproduced or distributed in any form or by

any means, or stored in a database or retrieval system, without the prior explicitwritten permission of the publisher.

Further information and copies of this documentation may be obtained from:

Computers and Structures, Inc.

1995 University Avenue

Berkeley, California 94704 USA

Phone: (510) 649-2200

FAX: (510) 649-2299

e-mail: [email protected] (for general questions)e-mail: [email protected] (for technical support questions)

web: www.csiberkeley.com
http://www.csiberkeley.com/http://www.csiberkeley.com/


3/6

DISCLAIMER

CONSIDERABLE TIME, EFFORT AND EXPENSE HAVE GONE INTO THE

DEVELOPMENT AND TESTING OF THIS SOFTWARE. HOWEVER, THE USER

ACCEPTS AND UNDERSTANDS THAT NO WARRANTY IS EXPRESSED ORIMPLIED BY THE DEVELOPERS OR THE DISTRIBUTORS ON THE ACCURACY OR

THE RELIABILITY OF THIS PRODUCT.

THIS PRODUCT IS A PRACTICAL AND POWERFUL TOOL FOR STRUCTURAL

DESIGN. HOWEVER, THE USER MUST EXPLICITLY UNDERSTAND THE BASIC

ASSUMPTIONS OF THE SOFTWARE MODELING, ANALYSIS, AND DESIGN

ALGORITHMS AND COMPENSATE FOR THE ASPECTS THAT ARE NOTADDRESSED.

THE INFORMATION PRODUCED BY THE SOFTWARE MUST BE CHECKED BY A

QUALIFIED AND EXPERIENCED ENGINEER. THE ENGINEER MUST

INDEPENDENTLY VERIFY THE RESULTS AND TAKE PROFESSIONAL

RESPONSIBILITY FOR THE INFORMATION THAT IS USED.


4/6


5/6

1

Table and Field Name Overwrites XML File

1 GeneralThe program maintains both a key and a name for each table and for each field in

each table. The table and field keys are predefined by the program and cannot be

changed; the program uses the keys internally when working with the tables. Theprogram uses the table and field names for all table export and display actions.

By default, each table and field name is the same as its corresponding key.

However, the user can change the table and field names using the table and fieldname overwrites XML file, as described in this documentation.

By default, table and field names are revised based on the content of a file

named xxxDefaultTableNameFile.xml. When the program launches, it reads the

xxxDefaultTableNameFile.xml file. If the xxxDefaultTableNameFile.xml file doesnot exist (see Note), or if it is empty, the table and field names remain the same

as the keys. The Options menu > Database > Set Current Table NameSource command can be used at any time to specify that table and field names

be based on an .xml file other than the xxxDefaultTableNameFile.xml. Thecommand also allows the user to restore the program defaults.

Any table name can be specified for a table; however, each table name must beunique compared to all other table names. Similarly, any field name can be

specified; however, each field name in a table must be unique. If the programreads non-unique table or field names, it will provide a warning message and set

the name back to its default; that is, the program will set the table or field name

to be the same as the associated key. The comparison of names for uniqueness isnot case sensitive.

Note: The default xxxDefaultTableNameFile.xml must be located in the samedirectory as the program executable file. The "xxx" is Sap, Etabs or Safe,depending on the program in use. The following table identifies the .xml file and

the executable file for each CSi Program.

Program-Specific XML File Name and Program Executable File Name

Program XML File Program Executable File

SAP2000 SapDefaultTableNameFile.xml Sap2000.exe

ETABS EtabsDefaultTableNameFile.xml Etabs.exe

SAFE SafeDefaultTableNameFile.xml Safe.exe

The use of the Table and Filed Name Overwrites file is currently available for

SAP2000 Version 12 and later and SAFE Version 12 and later. It will becomeavailable for ETABS with the next major release of the software.

2 SchemaThe schema is in the file named xxxDefaultTableNameFile.xsd, which is located inthe same directory as the program executable file (see preceding table). Again

xxx is Sap, Etabs or Safe, depending on the program in use.


6/6

Table and Field Name Overwrites XML File

2

3 Description of Simple ElementsElement Description

AssumedValue*

tkey The table key as predefined by the program. N.A.tname The new table name. Same as tkey

fkey The field key as predefined by the program. N.A.

fname The new field name. N.A.

* value assumed by program if the simple element is not included in the

complex element

4 ExampleFollowing is an example Table and Field Name Overwrites XML file: This filemodifies the Sap2000 Joint Coordinates table name to JCs and modifies the XorR

and the Z field names in that table to X and Zee, respectively. It also modifies

the name of the JointI field in the Connectivity - Frame table to JtI.

Joint CoordinatesJCsXorR

XZZee

Connectivity - FrameJointIJtI

table and field name over writes xml file

Documents