Errors Handling Depending on the Database Type

The type of the default database influences the runtime error handling. If a default database is specified with the help of the DATABASE statement, the runtime error handling depends on the fact whether the default database is ANSI-compliant.

 

The behavior of the errors depends on the specific SQL statement used rather than on the ANSI-compliant status of the database at runtime. If a program is compiled against a not ANSI-compliant database and then run against an ANSI-compliant database, the errors will behave as they behave in a non-ANSI-compliant database.

 

When the ANSI-compliant behavior is requested with no WHENEVER ERROR CONTINUE statement in effect, ANSI compliance will be in effect if one of the following conditions is true:

• the default database is ANSI-compliant
• the –ansi compilation flag is specified when compiling in console mode
• the DBANSIWARN variable is set

 

The non-ANSI-compliant method with no WHENEVER ERROR CONTINUE statement will take place if:

• the –anyerr compilation flag is specified when compiling in console mode (STOP is the default action)
• the –anyerr compilation flag is not specified (the default action after expression or data type conversion errors is CONTINUE, in other cases the default action is STOP)

 

If one part of an application is compiled in a non-ANSI-compliant database and the other in ANSI-compliant one, different parts will have different error handling.

 

There are several additional issues that concern database connections:

• You can include CONNECT, SET CONNECT and DISCONNECT SQL statements in a 4GL application, they cannot be prepared.
• To connect a 32-bit 4GL client to a 64-bit database server, use network connection and not the shared-memory connection.