Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 17 » UltraLite - Database Management and Developer Guide » UltraLite database connections

UltraLite file path formats in connection parameters

The physical storage of your device determines whether the database is saved as a file and what naming conventions you must follow when identifying your database.

Note Use absolute file paths when using the UltraLite engine to support multi-process access to a database since the engine may be started in different locations.

The DBF parameter is most appropriate when targeting a single deployment platform or when using UltraLite desktop administration tools. For example:

ulload -c DBF=sample.udb sample.xml
Note You can use the UltraLite administration tools to administer databases already deployed to an attached device.

Otherwise, if you are writing a cross-platform application, use the platform-specific DBF connection parameters to construct a universal connection string. For example:

Connection = DatabaseManager::OpenConnection("UID=JDoe;PWD=ULdb;device:DBF=\database\MobileDB.udb;desktop:DBF=DesktopDB.udb")
Platforms other than Windows Mobile

Either absolute or relative paths are allowed.

Windows Mobile

Windows Mobile devices require absolute paths.

You can administer a Windows Mobile database on either the desktop or the attached device. To administer a database on a Windows Mobile device, ensure you prefix the absolute path with wce:\. For example, using the ulunload utility:

ulunload -c DBF=wce:\UltraLite\myULdb.udb c:\out\ce.xml

In this example, UltraLite unloads the database from the Windows Mobile device to the ce.xml file in the Windows desktop folder of c:\out.