Teach you how to upgrade to SQL Anywhere10 (13)

Initializing/Extracting an Ultralite database from the SQL anywhere reference database on the command line

1, please read carefully the important things in software upgrades.

2. Ensure that Ultralite version 10 utilities in the system path precede previous versions of the utility.

3, make sure you have upgraded the SQL anywhere database and prepare it based on ultralite usage. If you need to upgrade your publication, be sure to do so before rebuilding the Ultralite database.

4, open a command line terminal and run the Initialization Database utility (Ulinit) to extract the Ultralite database. Please use the following statement:

ulinit -a "SAconnection-string"
-c "ULconnection-string"
-n pubname [ options

Make sure you have:

· Provides a connection string for the SQL Anywhere reference database and the new Ultralite database.

· The named publication contains the tables that are required by the Ultralite database. If you need to extract all the tables, use-n*.

Other options please decide on demand.

Previous versions of Ultralite applications must be regenerated with the version 10 API. These APIs have made significant improvements at the bottom, requiring you to change the code first and then regenerate the application.

Before you begin, make sure that you have carefully read the new Ultralite features to confirm how you need to modify the APIs you are using.

Porting the code for Ultralite application to version 10

Special Application Upgrade Considerations

· The connection code needs to be updated. For most APIs, you might want to use a connection parameter control. Only

The UltraLite for Appforge requires you to use the new control. For example, in an ultralite for Mobilevb version 9.x project, the Ulconnectionparms object carried in the Uldatabasemanager *withparms method is no longer supported. You must rewrite the code and use the Ulconnectionparms.tostring () method instead.

The connection parameter control makes it easy to combine a series of connection parameters. The Ultralite runtime converts the grouped arguments to strings. In addition to the Ultralite for Appforge API, you can still use connection objects. However, the connection parameter control provides a better way to diagnose the connection string error. See the Ultralite documentation for more information.

· UltraLite mode is now integrated into a database table and is no longer a separate. USM file. This means that you cannot use this file to create a database on a device. The new database creation function/method has been added. However, this method may increase the size of the application. To avoid application bloat, create a database using administrative Tools on your desktop now and then deploy it to your application.

· In this release, UltraLite always makes validation effective and supports up to 4 user IDs and passwords. However, if you do not need to persist validation in the database, do not create or provide a user ID and password. If no user name and password are provided, Ultralite defaults to provide UID=DBA, Pwd=sql.

• The Ultralite for Appforge component of version 10 replaces the previous version of the Ultralite for Mobilevb. You cannot use more than one version of a component on the same machine. Otherwise, Appforge cannot compile the VB project and produce the following error

Miss:

"Error importing Ulmvbctl9.dll." Unable to load "

Therefore, you must uninstall the 9.x version of the component.

Also, if a user has 9.x Ultralite for Mobile VB client on their device, you must uninstall and then install the Ultralite for Appforge client with version 10.

· If you have more than one embedded SQL file, you must continue to use SQL and processing (SQLPP) to generate A/C + + source file individually.

The Ultralite database now directly supports embedded SQL.

· Support for Unicode is different from the original version. The version 10 database uses UTF-8 encoding to encode multibyte characters. This way, you no longer need to plan for a Unicode database running in a non-Unicode run-time environment.