An assembly of connection parameters supplied in any application's connection code (be it an administration tool or a custom UltraLite application) is called a connection string. In some cases, applications parse the fields of a ConnectionParms object into a string. In others however, you type a connection string on a single line with the parameter names and values separated by semicolons:
The UltraLite runtime ensures the parameters are assembled into a connection string before establishing a connection with it. For example, if you use the ulload utility, the following connection string is used to load new XML data into an existing database. You cannot connect to the named database file until you supply this string:
ulload -c "DBF=sample.udb;UID=DBA;PWD=sql" sample.xml
UltraLite does not ignore unrecognized connection string parameters. Instead, it generates an error for unrecognized connection parameters.
All of the UltraLite administration tools follow a specific order of parameter precedence:
If specified, CE_FILE, NT_FILE, SYMBIAN_FILE, and PALM_FILE parameters always take precedence over DBF.
If you use two DBF parameters concurrently, the last one specified takes precedence.
If you supply duplicate parameters in a connection string, the last one supplied is used. All others are ignored.
Parameters in the connection string take precedence over those supplied in ULSQLCONNECT or a connection object.
ULSQLCONNECT environment variable is then checked to supply parameters that are not supplied in the connection string.
If no value for both UID and PWD is supplied in either the connection string or ULSQLCONNECT, the defaults of UID=DBA and PWD=sql are assumed.
Any leading spaces and/or trailing spaces in connection string parameter values are ignored. All connection string parameters cannot include leading single quotes ('), leading double quotes ("), or semicolons (;).
Specifying file paths in an UltraLite connection parameter