Prompt the end user at connection time when you require a user to authenticate as one of the four supported database users. The UltraLite graphical administration tools use a connection object.

Where possible, use either the ULConnectionParms or ConnectionParms object. It provides easier checking and a more systematic interface than using a connection string that is an argument for the Open method. See:

• UltraLite.NET: Authenticating users
• UltraLite C/C++ : Authenticating users
• UltraLite for M-Business Anywhere: Authenticating users
• UltraLite for embedded SQL: Authenticating users

Use a connection string if user authentication is not required. Common reasons for not authenticating a user may be because the deployment is to a single-user device, or that it is too awkward to prompt a user each time they start the application. The UltraLite command line utilities typically use a connection string if a connection to a database is required. You can also program your UltraLite application to read the values from a stored file, or hard code it into your application. See:

• UltraLite.NET: Connecting to a database
• UltraLite C/C++ : Connecting to a database
• UltraLite for M-Business Anywhere: Connecting to an UltraLite database
• UltraLite for embedded SQL: Connecting to a database

Use the ULSQLCONNECT environment variable if you want to store connection parameters you use repeatedly. By storing parameters, you don't need to provide them repeatedly during the development phase. Values you supply as a parameter in ULSQLCONNECT become defaults for the UltraLite desktop administration tools.

All UltraLite desktop administration tools check the ULSQLCONNECT values for any missing parameters not supplied in a connection string, following parameter precedence rules. To override these values, supply the alternate value in the connection string. See Storing UltraLite parameters with the ULSQLCONNECT environment variable.