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

SQL Anywhere 10.0.1 » SQL Anywhere 10 - Changes and Upgrading » What's New in Version 10.0.0 » MobiLink » Behavior changes and deprecated features

MobiLink server changes Next Page

MobiLink client changes


MobiLink user names and remote IDs

MobiLink now generates a unique ID called a remote ID the first time a remote database synchronizes (or when it encounters a NULL value for the remote ID). The MobiLink user name no longer needs to be unique. The MobiLink user name can now be considered a true user name that is used for authentication.

In previous versions, the synchronization progress was stored for the MobiLink user name. Now, the progress is stored for the remote ID and subscription for SQL Anywhere remotes, and the remote ID and publication for UltraLite remotes.

See ml_subscription.

Previously, you used the MobiLink user name to uniquely identify a remote database. The remote ID is a useful way to identify the remote database when you want a MobiLink user to synchronize multiple remote databases. In UltraLite remote databases, the remote ID is also useful for multiple MobiLink users to synchronize the same remote database.

See Remote IDs.

UltraLite clients

See Behavior changes and deprecated features.

SQL Anywhere clients