Version 6.68.00

This version of Theatre Manager contains one small change - the ability for the database administrator to set the locking mechanism for single user mode

Version 6.67 • Updates

Released July 15, 2005

 Key changes:
  • lets database administrator set the locking mechanism. Default is set to safest.

Note: Read prior release notes for any mandatory web pages changes. There are no web page changes for this version.
Preparing for the Update

Theatre Manager will

The user will need to

Before upgrade
After upgrade
  • None
Optional Steps
  • Go to the setup->System preferences window and alter the database locking preferences to meet the needs of yout site. Only change this setting on advice of technical support
Time Required
  • Updating the database from 6.65 will take less than a minute

System Preferences

Added two new settings in system preferences to allow the site database administrator to set the locking mechanisms for their venue. The recommended settings are shown below and should be changed under advice from technical support. The meaning of the settings are:

Overall Single User Mode Always user multi user mode This setting means that Theatre Manager will always use multi user mode for all operations. It is the safest mode and should be used if a site experience freeblock messages frequently. This mode will never attempt to take exclusive use of the database.
Check single user flag This mode checks an internal flag in the database for other users - before offering to go into single user mode. This is quite safe. However, if you cannot get single user mode, you may need to have everybody quit the database and/or restart the data bridge.
Check $shared bit This mode tries to obtain completely exclusive use of the database and will prevent other users from even logging in or finding the database. This mode may be used for non-data bridge with limited effects. It is not recommended for data bridge users
Both Do not use this setting unless advised by Arts Management Technical support. It should rarely ever be used.
Single User Mode: Plays Always Assume Multi User This mode will never take exclusive use of the database when adding a new event. This is the recommended setting for normal, day-to-day operations
Same as overall Single User Mode

In this setting, creation of events may be 3 - 4 times faster, if the 'Overall Single User Mode' is set to 'Check Single User Flag' or 'Check $shared bit. It is advisable to only make this setting change when creating your events for the season AND if you have made sure nobody else is using the database. When done, please set this back to the 'Always Assume Multi User' mode.

If, however, the 'Overall Single User Mode' is set to 'Always user multi user mode', then this flag has no effect. It may be best to leave it at this mode in these situations, so that you only have to change the 'Overall Single User Mode' flag to 'Check Single User Flag' when building events in mass mode (temporary measure at season creation time).

 

Misc Changes