Advantage TDataSet Descendant
Server name (or drive letter) to which to connect. If the application uses a server name as the parameter, it must include the share name as well. For example, user "\\SERVER\SHARE" or "SERVER\VOL".
If connecting to a data dictionary, this path must also contain the dictionary file name, for example "\\myserver\myshare\data\mydictionary.add". See Accessing an Advantage Data Dictionary with the Advantage TDataSet Descendant for details on making a data dictionary connection.
If the current working directory is to be used, specify a "." rather than leave the property empty.
The connection path can be provided in many formats. Drive letters are accepted, as well as UNC and direct Linux paths. Advantage considers any slash (forward or backslash) to be a path delimiter. All of the following are valid connection paths, although UNC is the recommended format:
/mydata (Linux clients using Advantage Local Server only)
x:\mydata (all clients excluding Linux)
If using local server from a Linux client see the REPLACE_UNC_SERVER section in ads.ini File Support for details on how to map a UNC server name to a local mount.
Connection paths to the Advantage Database Server can also include a port number if the Advantage Database Server configuration specifies the port number. The form of the connection string can be either of the following (using forward or backward slashes):
In the first format (//servername:port), the client will attempt a DNS lookup for the host to find the IP address and then will use the given port to attempt communication with the Advantage Database Server. In the second format, the client simply uses the given IP address and port to attempt to communicate with the Advantage Database Server. The following are syntactically correct connection paths using port numbers:
property ConnectPath: String;
The string specified is usually the database directory.
To open an Advantage Data Dictionary connection, specify the full path to the .add file (for example, "c:\data\myfirstdd.add").