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

Tip

You can use the UltraLite administration tools to administer databases already deployed to an attached device. See Windows Mobile.

Otherwise, if you are writing a cross-platform application, use the platform-specific (CE_DBF or NT_DBF) file connection parameters to construct a universal connection string. For example:

Connection = DatabaseManager::OpenConnection("UID=JDoe;PWD=ULdb;CE_DBF=\database\MyCEDB.udb;NT_FILE=MyDB.udb")

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.

If you are using the ulunloadold or ulunload utilities to administer a database on the Windows Mobile device directly, UltraLite cannot back up the database before the unload or action occurs. You must perform this action manually before running these utilities.