13.1 Overview

This section outlines important details regarding the C and SQL/ODBC implementation used by Visual LANSA. You should be familiar with this section of the guide before designing and building your application database or new applications.

If you have never used SQL or ODBC before, i.e. you have only used LANSA/AD and are translating your application using Visual LANSA, you should take some time to learn some SQL/ODBC fundamentals.

Detailed knowledge of SQL/ODBC is not a requirement. LANSA insulates the developer from the specific platform requirements; however, knowledge of the target platform will assist you in developing your applications.

For example, SQL/ODBC has a number of keywords which have special meaning to SQL/ODBC. These keywords (e.g. ADD, COMMENT, INSERT) are reserved and cannot be used as field names in an SQL/ODBC table. Again, LANSA will insulate you from this using automatic renaming facilities; however, when designing your database or when accessing the SQL/ODBC tables directly, this type of knowledge will be helpful.

A partition identifier containing the special characters "$@" (in this sequence) will NOT be supported. This is the result of restrictions when using a "make" file to compile and link Visual LANSA objects.

For example a partition identifier of "L$@" is NOT supported, but "L@$", "LX@" and "L$X" are supported.

Use of an "@" sign anywhere in a partition name under Windows environments is not supported and you should avoid using partitions that have an "@" sign in their name when working with Windows.

 

Portability Considerations

Note: A recommended portability standard for all partitions identifiers is to use letters of the English alphabet (A - Z) and numbers (0 - 9) only.