Between all databases, "cultural" differences exist; this means that you must adapt the application or database when you change databases.
The Upsizing Wizard itself takes care of these differences and performs conversions where necessary. However, sometimes the Upsizing Wizard may not be able to proceed without your assistance. Depending on the syntactical differences between Microsoft Access and ADABAS, it may be necessary for you to participate in the conversion of default values and validation rules.
Certain initialization constants and functions are not automatically transferred. In this case, the Upsizing Wizard opens a window containing the DDL expression that was used when attempting to transfer this initialization to the table in the server database.
For the complete list of functions provided in ADABAS, their syntax and notation, refer to the ADABAS reference manuals.
Microsoft Access and the ADABAS server database do not use the same syntax for time/date constants.
If you would like to initialize a column with a date constant and meet up with a specific error message during the migration process, change the time constant at the end of the ALTER TABLE statement from the Microsoft Access format to the ADABAS format "yyyy-mm-dd-hh:mm:ss". For example:
'1990-01-01-00:00:00'
Unlike Microsoft Access, ADABAS always requires that you specify the date and time in a TIMESTAMP column (date/time column). If the date alone is always specified in a column, the "date" data type must be used for this column. If necessary, the user must make this change after the migration process is completed.