Supplying UltraLite connection parameters

Connection details can be collected via different methods, depending on whether you are connecting from a custom UltraLite application or from one of the SQL Anywhere administration tools for UltraLite.

Method

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.

You can use the UltraLite.Net ULConnectionParms object or the UltraLite for M-Business Anywhere ConnectionParms object to aid connection parameter collection and inspection. See:

Use a fixed 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:

dbisql is the only tool that supports ULSQLCONNECT. 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.

1 Typically user-supplied.

2 For desktop administration tools only.

3 Typically hard coded or stored in a file.

 See also