|
CoreReader
The Universal Access Data Utility |
|
|
home page description documentation countries source specifics policy letter |
|
license free software change log testing requirements database manager date protocol |
|
Disclaimer Brand names are addressed only as a service to CoreReader users. See the source specifics page for details. To add to these notes or to add your favorite data source, see instructions on the source specifics page.
Source Developer's past experience.
Running With Interbase After reviewing my very old Delphi code, it appears that CoreReader will operate InterBase without problems, but I no longer have InterBase running to test it. Interbase was intentionally written to ANSI standards by the Borland team, so you ought to be able to make it jump through hoops if it has not recently deviated. Recent versions unfortunately allow extraneous non-standard characters in object names. That problem can be circumvented through the use of CoreReader's configuration parameters. It appears that perhaps quotation characters should be used as delimiters instead of the standard apostrophe. Also, refer to the Firebird notes. Firebird is an open source product that was spun off from InterBase. The data socket that was reportedly used to connect CoreReader to Firebird version 1 was the XTG ODBC driver (beta 16). Many data sockets may be used to connect to InterBase and to Firebird. Three of the free ones are the XTG driver, the ODBC/JDBC (Starkey) driver, and the IBPhoenix driver. These data sockets use non-standard connection parameters such as the DBNAME instead of DATABASE. Therefore, a connection string must be used instead of entering parameters into the boxes. A connection string using the IBPhoenix data socket might look something like this:
A connection string using the XTG data socket might look something like this:
|
|
This web site is maintained with Notepad. |
|
|
Copyright 2001 - 2010 John Ragan. |
|