|
Previous UltraLite applications must be rebuilt with new version 10.0.1 APIs. Since the introduction of UltraLite 10.0.0, these APIs have undergone significant enhancements which require that you first make code changes (if applicable) and then rebuild the application.
Before you begin, however, ensure you have closely reviewed UltraLite new features to see what changes have been made to the API you have employed.
Your connection code needs to be updated. For most APIs, you should try to use the connection parameter control. Only UltraLite for AppForge requires that you use the new control. For example, in UltraLite for MobileVB projects version 9.x, the ULDatabaseManager *WithParms methods that took a ULConnectionParms object are no longer supported. Instead, you must rewrite this code to use the ULConnectionParms.ToString() method.
A connection parameter control assembles a set of connection parameters conveniently. The UltraLite runtime in turn transforms the assembled parameters into a connection string. For all APIs other than the UltraLite for AppForge API, you can still use a connection object. However, the connection parameter control provides better diagnosis of connection string errors. For API specific details see:
The UltraLite schema is now integrated into the database as tables, rather than as a separate .usm file. This means you cannot create a database on device using this file. Instead, a new database creation function/method has been added. However, this method can increase the size of your application. To avoid application bloat, use an administration tool to create the database on the desktop first and deploy it to your application at a later time. See UltraLite desktop creation.
UltraLite always has authentication enabled in this version and can support up to four user IDs and passwords. However, if you do not want to maintain authentication in your database, do not create or supply any user IDs and passwords. UltraLite always supplies the defaults of UID=DBA and PWD=sql if none are supplied. See Interpreting user ID and password combinations.
The 10.0 UltraLite for AppForge component replaces previous versions of UltraLite for MobileVB. You cannot use more then one version of the component on the same machine. If you try to do so, AppForge cannot compile your VB project and generates this error:
"Error importing ulmvbctl9.dll. Unable to load"
Consequently you must unregister 9.x versions of this component. See the table in UltraLite application code upgrade paths for details.
Additionally, if a user has a 9.x UltraLite UltraLite for MobileVB client on their device, they must remove it before trying to install and use the 10.0.1 UltraLite for AppForge client.
If you have multiple embedded SQL files, you must still preprocess each one of them using the SQL preprocessor (sqlpp) to create your C/C++ source files. However, you no longer need to use a reference database. UltraLite databases now support embedded SQL directly.
Unicode characters are not supported in the same way as in previous versions. Instead, version 10.0.1 UltraLite databases use UTF-8 encoding for multi-byte characters. As a result, you no longer need to plan for a Unicode database running on a non-Unicode runtime.
UltraLite application code upgrade paths
UltraLite application code upgrade tools