If you intend to allow multiple users to have access to and manage your data, you will want to configure your installation in a way that makes this easier to accomplish.

RealTime uses 3 directory folders for information management … an [Installation] directory, a [Data Root] directory, and a [Data] directory.

• The [Installation] directory is usually on a local hard drive for performance reasons and to avoid conflicts with other users.  This directory will hold calculated values that align with the current user settings. (i.e. C:\RT3.1)

• The [Data Root] directory holds shared information such as the list of companies, authorized users and other items.  (i.e. for example: C:\RT3.1, or via a UNC file://Server/Drive/DataRoot or mapped drive that points to the server)

• The [Data] directory holds the actual data, including employees, transactions, schedules, and more. (i.e. file://Server/Drive/DataRoot/Data

It is recommended that the Program is installed to a Local Disk for all users (i.e. C:\RT3.1).  You will need to have administrative rights to install, but do not need to be an administrator to run RealTime.  If your user’ rights are especially restricted, however, we will have to enable rights to certain registry keys.

When setting up your network environment, you are going to want the [Data Root] directory to be a location that is readily available to all RealTime users.  For simplicity, we recommend using UNC names for access to shared directories … however, for the [Data Root] directory it is not necessary for the “full path” to it be identical for all users.

When setting up your [Data] directory (during the creation of a “Company”) you must ensure that the full path of the [Data] directory is viable for all users that share the same [Data Root] directory.  UNC names work well here but if you use Mapped Drive Letters, you must be certain that the mapping is consistent for all users and that the mapped drives are retained when the computer is restarted.

Terminology breakdown:

On the [Installation] directory side of the scenario:

The RT3.1 folder should be created off the local drive on each machine.  By default this would be C:\RT3.1.  On the [Data Root] directory side of the scenario (Reference Example 1 diagram):

• You want both the Server and the Workstation installations to point to the same [Data Root] folder location.
• This location should have within it a Microsoft Access database file created upon installation named [COMPANY3. MDB] among other things.
• It’s recommended that you use a UNC path to the [Data Root] folder … this requires sharing the path … even the Server should use this UNC path to point to itself rather than using a local drive designation.

NOTE: The COMPANY3.MDB file contains the company’s information and helps point the system to the appropriate [Data] folder.  All installations should be pointing to the same COMPANY3.MDB file.

On the [Data] directory side of the scenario:

• You want both the Server and the Workstation installations to point to the same [Data] folder location … this should be achieved as long as the appropriate COMPANY3.MDB file is found.
• The [Data] folder would be synonymous with the Clock/Terminal Name field referenced within the [Company Setup] area of RealTime
• This location should have within it the files associated with Microsoft Access files …

So therefore:

1. Install the program on the server
2. Enter the name of the Company and the Clock/Terminal folder to be used and hit the [Tab] key
3. In the Directory field go through the steps required to setup the path to the [Data] folder on the Server using the […] browse button to access the [Data Root] folder using the My Network Places route to ensure a UNC referenced path on each machine.  The Clock/Terminal folder (i.e. [Data] folder) should be located within the [Data Root] folder and its name will correspond with whatever you’ve named the Clock/Terminal.