How to set up a pilot programme to test MonTel 32bit client

This application note is for sites that wish to test the 32bit client, before pushing it out to all users.

You can run a 16bit MonTel system along side a 32bit System with no problems except that the disbursement records generated by users of the Pilot program, and client record updates they make will eventually be lost, when you bring the rest of the users over. Since the server remains the same and the changes inside the PABX.INI file are minimal, it may be run safely from the same directory as the existing 16bit client.

The installation of code, does not overwrite exiting 16bit programs, with the following exception: You must be also running the most recent version of the 16 bit client (and the latest version of the server) that uses the most recent costing tables, as the costing tables, and the INF files are shared (and the same in the most recent version).

To summarise:

• All call records will be retained - as these are generated by the users.
• All "My Calls" will be retained - as these are generated by the users.
• The PABX.INI file and user settings will remain the same, except that there are some entries added. These entries are not used by the 16 bit client.
• The executables all have different names.
• The only major issue is the Master Client data base. The change here is one way and affects all users. So we need to copy this file, and acknowledge that once we are finished testing we will be throwing it away and replacing it with the existing data from the 16 bit database.

Here are the steps:

1. Check that you have the latest 16bit version.
2. Copy the new files from the distribution media to the MonTel Application directory.
3. In the MonTel data directory, under ClientDB, copy CLIENTDB.MDB to CLIENT32.MDB.
4. Add the following entries and/or sections to existing PABX.INI file. Make sure that the timezone section is correct. Note that the Master Client Database is now CLIENT32.MDB, and therefore is NOT shared with the 16bit users.

[Program]

Montel32HelpFile = {MonTel App path}\Montel32.hlp

[ClientDB]

Local32DatabaseName = {same as LocalDatabaseName}

Client32DatabaseName = CLIENT32

[ISAM32]

MaxBufferSize =0

PageTimeout=5000

LockRetry=20

SystemDB=""

Threads=3

UserCommitSync="yes"

ImplicitCommitSync="yes"

SharedAsyncDelay=5

ExclusiveAsyncDelay=2000

FlushTransactionTimeout=500

MaxLocksPerFile=9500

LockDelay=100

RecycleLVs=0

Finally, from the Setup32 directory in the MonTel Application directory, run Setup. This will add the local and runtime files.

Then start up MonTel32.exe from the MonTel Application directory, and run through the normal upgrade prompts. One the (copy of the ) Master Database has been upgraded you should be able to run the MonTel 32 bit client.

It may be that you need to re-boot the computer before running the MonTel 32 bit client. Sometimes the Netwiz Font is not activated without a reboot, causing call record displays to have Zero height.

Check it though on your machine.

You can then deploy it to a small number of users, hopefully using different types of machines. I would suggest not more than 5, since the client data collect will be lost when you do the final upgrade.