UltraLite Database User's Guide
Synchronization for UltraLite Applications
Designing synchronization for your UltraLite database
Maintaining primary key uniqueness
Default values are chosen from the partition identified by the global database identification number until the maximum value is reached. When this state has been reached or is imminent, you must assign the database a new identification number.
The programming interfaces provide means of obtaining the proportion of numbers that have been used. The return value is a short in the range 0-100 that represents the percent of values used thus far. For example, a value of 99 indicates that very few unused values remain and the database should be assigned a new identification number.
The method of setting this identification number varies according to the programming interface you are using.
UltraLite for MobileVB See Properties.
UltraLite ActiveX See Properties.
Native UltraLite for Java See ianywhere.native_ultralite.Connection.databaseID in the API Reference.
UltraLite.NET See Connection in the UltraLite.NET API Reference.
Embedded SQL See ULGlobalAutoincUsage function.
Static C++ API See GlobalAutoincUsage method.
Static Java API See globalAutoincUsage method.