This version of our software has provided the ability to work in a multiuser mode. To allow this to happen, the software provides the ability to move your databases to any location and then have all machines point to that database. It is important that the moving and repointing of databases be done via the software. You can copy and paste the database from your current hard drive to the LAN then repoint your machines, but this then destroys the relationships to be discussed below. Always move your databases and point to them via the software’s built in functions.
When you first view this screen, you will see the database file in the directory in which you installed the software. After it in brackets will be the words (Master Database). If you are running your software allowing replications (you control that as a business rule), there will be one (1) Master Database in your system, and multiple replicas. All users can access this database and make updates to it. Users can also create replicas on their own machines, work on the replica database (at home, at the scorekeepers table, etc) and later synchronize there database changes with the Master database.
In this diagram, the Master Database is on a central server. The admin and scheduling computers are connected to the LAN and their version of the software updates the Master Database directly. A Laptop, also connected to the LAN, has made a Replica Database on its own machine. The Laptop can now be disconnected from the LAN, used in any capacity desired, then reconnected to the LAN and when synchronized, all changed data on the Laptop will be replicated to the Master Database and any changes to the Master Database since the last replication or synchronization, will be made to the Laptop Replica Database. If desired, once the Laptop has created a replica on its local drive, it would never have to work on the Master Database again, it could continue working with its replica and synchronize data when required. It is important be aware of Microsoft Accesses 30 day synchronization limit. Any changes made to a replica database and not synchronized within 30 days will not be able to synchronize.
In order to manage this multiuser scenario, the software has built-in functions to accomplish the setting up and maintenance of the system. You should never have to go into your file manager and manually move or rename files.
With this function, you can change the database you wish to point to on the fly. This function would be performed if a user, that is currently working on a single user local database or a replica database wishes to connect to the Master Database (and visa-versa). This feature is also provided on the Preferences screen so that users can use this feature without requiring access to all other administration functions. The database name must always be lafspdb.mdb, but may reside in any directory. Click Browse to select a database in a different directory. When selected, the new database path will appear on the screen. If it is correct, then click the ‘Change Database File’ button. Since a new database is being initialized, all data not saved in the current database will be lost. You will be warned of this. If a connection to the new database has been made successfully, then all data in your system will now be of the new database.
The database you last used is always the default on start up. After the application is open you can always use this function to change databases. However, you have the option to select a database every time you start the application. From the Help select on the Menu Bar, if you select ‘Show DB File Dialogue on Startup’, then every time the application is started, you will be asked which database file you wish to use. This dialogue will also appear if the application is opened and the database file that was last used, no longer exists (i.e. a LAN database was moved). This feature ensures that the application will never stop functioning due to database problems.
With this function, you can move a database, on the fly, from one location to another. The primary reason for this would be to move your database from your local drive to a LAN so that you can begin to run the application in a multiuser or replication mode. You may also just wish to move your Master Database to a new location. If you do this, when your users try to connect to the previous database location, the database will not be found, and a search dialogue box will be presented for users point to the new Master Database. This dialogue will be presented to a user every time they login into the software and the previous database file they were working on cannot be found. It makes sense that you try to move your Master Database as infrequently as possible.
To move the database, click Browse to select a new directory. When selected, the new database path will appear on the screen. If it is correct, then click the ‘Move Database’ button. Since the database is being moved it needs to be closed then reopened and therefore all data not saved in the current application will be lost. You will be warned of this. If a connection to the moved database has been made successfully you will receive a confirmation message.
The third section on this tab is a section with a checkbox to turn on/off security. Check this box and click the ‘Change Security’ button will invoke user login security on the database that you are currently logged into. With this version of the software you can point to different database files. Security is set at the Database Level. Once security is enabled, every time a user wishes to access this database, they will be required to enter a valid user id and password. Once you have enabled security, you will see two new tabs appear, the Users and User Groups Tabs. If you turn login security off, the two tabs disappear and login is no longer required for the database.
This is now an obsolete function. The software always supports multiuser mode.
Now that the software is set up for multiple users, the next step is connecting other machines to your database. This is accomplished in three steps. The first is to install the full version of our software on the new machine. Our registration keys are valid for only a single machine. They will not work on any other. After installing the software on the new machine, you must register that version. It will not point to any other database other than the one installed. You can also not access other administrative functionality to point to a new database until it is registered. Therefore, you will need to bring up the registration screen, copy the computer key and request a registration key from our site. Once you receive the registration key, enter it into the computer and the software is now registered. To access the Administration function, you will need to restart the software. However, you can use the Database Admin tab on the Preferences screen to point to the LAN database being shared. You can now use all the Administrative features to manage your networked software.