How is the Local Client database named and other issues

The Local Client Database is a Jet Engine (MS Access 97) database that has links to the master client database, and a number of queries. It does not store any client information. Therefore the Local Client database can be deleted and re-created at any time, with out any loss of data on the system.

Since data stored on the server is usually more robust (generally the server is not switched off unexpectedly, or crashes less often), corruption of the local client database is the most likely cause of problems, especially if only affecting one or two users.

It can be re-created in about about 10 or 15 seconds on typical machines. Generally, this is best set up as a fairly transparent process to the user, who will see a message box, with a progress bar, saying, "Updating the Local Client Database".

• The local client database will need to be updated (re-created) automatically by MonTel when:
• When MonTel cannot find a local client database on the computer.
• MonTel has been upgraded, and the Master Client database has been altered.
• The Master Client Database has been compressed or repaired.
• If UpdateLocalDBDailyOnStart or ForceUpdateLocalDBDailyOnStart are set to 1.
• ForceAllLocalDBToHaveTheSamePath = 0 and AlwaysUseDefaults = False, and the user has not specified a path for the Local client database, meaning the is no name specified in MONTEL.INI.

The last entry above can be the cause of some confusion, even for MonTel, since on occasions it may not be able to resolve this and loops continually failing to create a Local Client database. Here is the definitive order of actions for deciding the name of the Local Client Database.

Note DEFAULTS.INI in the MonTel Application Directory is used instead of MONTEL.INI in the Local Windows Directory when AlwaysUseDefaults = 1.

1. MonTel Resolves the PABX.INI file, and the correct MONTEL.INI file based on the settings of AlwaysUseDefaults, and the existence of Defaults.INI (or specific user Defaults.INI).
2. It now chooses to use either the combination of LocalDatabaseLocation and LocalDatabaseName from the PABX.INI file, OR ApplicationDatabase as a full path name from appropriate MONTEL.INI file.
3. If ForceAllLocalDBToHaveTheSamePath = 1 in the [ClientDB] section of PABX.INI then it uses the combination from the PABX.INI file.
4. If AlwaysUseDefaults = 1 then then it uses the combination from the PABX.INI file. In a sense this breaks the rules, as AlwaysUseDefaults refers only to the use of Defaults.INI. However, if there is only ever (one choice = no choice) a specific location from the Local Client Database, it makes no sense to prompt the user to select a location.
5. Otherwise it reads ApplicationDatabase from the MONTEL.INI file.
6. It then adds ".MDB" if required to the end of the name, and uses this name as the Local Client Database Full File and Path Name.

A loop may be caused here (and it is one of the most commonly reported problems) if MonTel concludes that the name is invalid (usually because it is blank), and wants to prompt the user for the correct name when either or both AlwaysUseDefaults = 1 or ForceAllLocalDBToHaveTheSamePath = 1.