CAPE with Windows 7 and Vista
CAPE software is compatible with all versions of Microsoft Windows, but some configurations are more straightforward to use than others.
In the table below, the numbers in square brackets refer to the notes that follow.
Operating System |
CAPE 2005 |
CAPE “2009” |
||
Interbase 6 |
Firebird 2.x |
Interbase 6 |
Firebird 2.x |
|
Windows 2000 |
[1] |
[4] |
[1] |
[1] |
Windows XP |
[1] |
[4] |
[1] |
[1] |
Windows Vista |
[2, 3] |
[2, 4] |
[3] |
[1] |
Windows 7 |
[2, 3] |
[2, 4] |
[3] |
[1] |
Notes
[1] This configuration works well, and does not require any special steps.
[2] Versions of CAPE 2005 with a “Last Revised Date” after July, 2007 are compatible with Windows Vista and Windows 7.
[3] When using Interbase 6 in conjunction with either Windows Vista or Windows 7, you must use a “remote” database path syntax. See the section below titled “Connecting to a Database.”
[4] When using Firebird 2.x in conjunction with a CAPE database schema < 3.50, the schema must be “patched” to be compatible with Firebird. If you require this configuration, please contact Electrocon for more information.
Connecting to a database
When connecting to a database file, you can use either a “local” or a “remote” path syntax.
Local database connection
A “local” path is the same as you would use to refer to any file located on the local computer.
<drive>:<path>\<dbfile.gdb>
For example:
c:\cape\dat\cape.gdb
This type of connection can be done using the CAPE Executive | File | Attach Database | Open File Dialog…
Note: When running CAPE + Interbase on a Windows Vista or Windows 7 machine, you must always use the “remote” syntax. There is an incompatibility between Interbase and these versions of Windows, which prevents the “local” connection from working properly. In this situation, use “localhost” as the remote database server name.
Remote database connection
Any computer can fill the role of database server as long as either Interbase or Firebird is installed and running, and TCP port 3050 is open.
Note: Connecting to a remote database using a mapped drive letter is NOT recommended. It may work in some situations, but it can also lead to database file corruption.
A “remote” path includes a specific reference to the database server. The syntax is specific to Interbase/Firebird, and is different from what is returned from standard file browsing. The remote path syntax looks like this:
<database_server_name>:<drive>:<path>\<dbfile.gdb>
Where:
<database_server_name> is the TCP host name of the database server
<drive> is the local hard drive letter on the server (NOT a mapped drive letter)
<path> is the file path
<dbfile.gdb> is the name of the database file
For example:
dbserver:c:\cape\dat\cape.gdb
Since this “remote” path syntax is not the same as is returned by the standard file browse dialogs, you must manually enter the database path to establish the connection. In CAPE Executive, type:
ready_db “dbserver:c:\cape\dat\cape.gdb”
When using CAPE 2009, an alternative remote path syntax is supported. You can use the standard file browse dialog to select a database located on a remote share point. Note that mapped drive letters are still NOT supported, but you can browse to:
And connect successfully.
If you have additional questions, please contact Electrocon for support.
