4.10.2 PC Other Files
LANSA supports most popular databases used in business at stable and supported versions. Refer to your LANSA supplier if you need exact details of what databases and versions are supported.
A PC Other file will always be loaded into an RDMLX partition as an RDMLX PC Other File. There is no option to load a PC Other file into an RDMLX partition as an RDML file. Furthermore, RDML field types will be converted to RDMLX field types. For example, alphanumeric fields become string fields.
When LANSA loads the file, it records the information required to connect to the database, which is then automatically used at execution time. These details may need to be altered. (Refer to Using DEFINE_DB_SERVER to modify connection details.)
- If LANSA cannot find a primary key defined for the file, it will load the first unique index (if any) it finds as the primary key.
- The Create RRNO Column flag must be set as appropriate for your application. Refer to Create RRNO Column.
- DateTime fields may require special handling. (Refer to Handling of Timestamp or DateTime columns.)
- It is strongly recommended that you do not load LANSA files as PC Other Files. Refer to LANSA Files loaded as PC Other Files.
- SuperServer PSXX parameters cannot be used with local PC Other Files. (Refer to Using SuperServer with PC Other Files.)
PC Other File data cannot be shipped with the Deployment Tool. If you need to ship data, you will need to write your own functions to insert or update the data as part of a package install. The Built-In Functions TRANSFORM_LIST and TRANSFORM_FILE may be appropriate. For further details, refer to Commands to Execute in the .
Also See
LANSA Files loaded as PC Other Files
Using SuperServer with PC Other Files
Using DEFINE_DB_SERVER to modify connection details
Load Other File in the