Migrating Clients
Go Up to Migrating to InterBase
To migrate an older client application to InterBase XE, install the InterBase XE client onto the platform where the client application resides. An InterBase server then recognizes that client as a version 6 dialect 1 client.
It is good practice to recompile and relink the application and make note of field names, data type use, and so on in the new application. When you recompile, state the dialect explicitly:
SET SQL DIALECT n;
- Important: If you have databases that use any of the new version 6 keywords as object identifiers and you are not migrating those databases to dialect 3, you might consider not migrating your version 5 clients. If you migrate them to version 6 dialect 1, you lose the ability to access those keyword columns. See New InterBase Keywords.
When you recompile an existing gpre
client, you must recompile it with the gpre
-sql_dialect
n
switch.
There are several paths that allow you to create dialect 3 clients that access all new InterBase 6 features:
- In Delphi, make calls to functions in the new InterBase Express (IBX) package. Because the Delphi beta includes InterBase 5, it ships with a version of IBX that does not include calls to the new InterBase XE Services, Install, and Licensing APIs.
- To write embedded SQL applications that address all InterBase XE dialect 3 functionality, compile them using
gpre
-sql_dialect 3
.
Client | How to migrate |
---|---|
Older applications such as InterBase version 5 applications |
|
isql |
-sql_dialect n
SET SQL DIALECT n; |
GPRE |
-sql_dialect n
EXEC SQL SET SQL DIALECT n; |
BDE |
All applications use SQL dialect 1. To access InterBase dialect 3 features from Delphi, use the IBX components. |
InterClient |
InterBase 6: All applications use SQL dialect 1. InterBase 7 introduced InterClient 3, which is a dialect 3 client. |
Direct API calls |
When you call isc_dsql_execute_immediate() ,
|