The startnewdatabasegeneration statement starts a new generation of the current database to the server (must be a shared database).


This statement has one parameter:

parameters – dictionary containing the new generation options, see the description below.


This statement starts the process of uploading a new generation of the current database to the server. The current database must already be shared on the server.

In its simplest form, this statement can be used with the uploadnewdatabasegeneration to upload a full new generation to the server. This is like checking all the boxes when you upload a new generation with the Database Options dialog (see Uploading a Critical New Generation on the Changing the Design of a Shared Database page). Note: This operation will only work if all other users have either closed this database or disconnected it from the server, if that’s not the case, the startnewdatabasegeneration statement will stop with an error.

startnewdatabasegeneration ""
... insert/delete fields, etc.
uploadnewdatabasegeneration ""

You can customize the new generation by supplying a dictionary with options. This example will make a new generation that only changes the procedures and forms, and leaves the dataand field structure untouched. This is a “non-critical” new generation so other users can continue to use the database. Since the data is not involved, the entire operation is performed by this statement – there’s no need for a follow-up uploadnewdatabasegeneration statement.

startnewdatabasegeneration initializedictionary(
    "NOTES","Fixed various bugs.")

There are four possible options that can be specified in the dictionary: COMPONENTS, URGENCY, SYNCMETHOD and NOTES:

To better understand these options, see Changing the Design of a Shared Database.

See Also


10.2NewNew in this version.