Default value for X_UPID may not be set automatically
If the X_UPID column is added to an MS Access table by LANSA (when Create RRNO Column is selected) and if the table will have inserts made by a non-LANSA program, you must manually ensure that a default value is set for X_UPID.
This is due to a limitation in some versions of MS Access that do not support the DEFAULT syntax in the ALTER TABLE statement. If this is not done and X_UPID is NULL, when LANSA attempts to update a row inserted by the non-LANSA program LANSA will always report a crossed-update validation error.
The default ODBC data source created by a Microsoft Access install is not suitable for use by Other Tables, as it does not provide all connection parameters for the chosen database. Thus, when you come to use your Microsoft Access Other Table, LANSA will supply to Microsoft Access an incomplete list of connection parameters, causing Microsoft Access to ask for the missing parameters. Every time you execute the application again, the Microsoft Access logon details will be asked for again.
There are two ways to address this issue. Firstly you can change the ODBC DSN to specify the missing information. This is the simplest and the most commonly used method. The second method is described in Using DEFINE_DB_SERVER to modify connection details.
SELECT command restrictions
LANSA does not support Generic(*Yes) or Options(*StartKey). If you attempt to use these options on a SELECT command against a Microsoft Access Other Table, you may get unexpected behavior.