Some typical directory structures are listed below, in order to provide a better overview of the Folder and directory hierarchy of various PC CADDIE installation scenarios.
These are particularly important for new acquisitions (server migration/new clients). The first priority is that all workstations on the network have access to the same main data.
Recommended directory structure:
Start by running C:\PCCADDIE\USER_1\PROGRAMM\PCC_WIN.EXE.
The “local data” is located on the individual workstation.
Typical directory structure:
|common data for all workstations|
Start by running C:\PCCADDIE\USER_1\PROGRAMM\PCC_WIN.EXE on each station.
You cannot longer work with files shared over the network (local server) if there are more than 5 running instances1) or terminal server installations. In this case it is necessary to install the Advantage Database Server (ADS) (remote server).
The PC CADDIE installation directory structure does not change when migrating from local server to remote server.
New version (used in Sempach and Weilrod)
PC CADDIE now automatically detects when there is a Terminal Server installation. The prerequisite for this is that PC CADDIE is started from the sub-folder /TSC/START/PCCADDIE/USER_1/PROGRAMM/. PC CADDIE then automatically searches for the corresponding /USERS/ folder and starts the PC CADDIE there.
PC CADDIE now automatically starts the user-related PC CADDIE or restores it if there is no PC CADDIE available for the Windows user. !The directory path must be defined exactly as described above!
It is meaningful and necessary that each client is assigned his own program directory in case PC CADDIE operates in a terminal server environment. This directory is used for storing individual data, such as hardware connection (control receipt printer, card reader, etc.) or even the design settings (font sizes, the size of the checkout mask, …).
For this purpose, the following directory structure is needed on the terminal server:
The „TSC“ folder contains one folder for each of the client's PCs which will connect via RDP with the terminal server; for example:
In addition, there should be a default folder (this ensures that PC CADDIE is started from this folder on the PCs that do not have a corresponding sub-directory):
This is why the name of the individual sub-folders must be the same as the name of the computers which will connect via Remote desktop connection to the terminal server.
The PC CADDIE program directory will be installed in these sub-directories
In addition, you need a free driver on the terminal server; this ensures that each client's folder can be connected as a virtual driver on the terminal server when PC CADDIE starts. You can find the batch file under http://www.pccaddie.com/dl/special/TSC/ (must be executed on the individual computers).
You should save this in the directory C:\PCCADDIE\TSC\_BAT. The symbol files are saved in the same place. So it is now possible to create a link to this batch and assign the PC CADDIE icon.
This results in the same directory structure for all computers, for example:
P:\PCCADDIE, where “P:” will be then linked to “C:\PCCADDIE\TSC\CLIENTNAME” using the SUBST command.
It is also recommended to run the “SAVE” macro on each of the workstations. This will copy the local directory configuration on the server.
As an alternative to the directory structure based on the PCs' names, you can also create a directory structure based on the usernames (mixing the two is also possible). This makes sense when a user frequently works from different PCs, but would still want to use his own environment, respectively “his own” PC CADDIE. We recommend the first variant, using computer names, especially for cash registers. This ensures that all the local hardware connection parameters are preserved (for example, receipt printer, card readers etc).
It is also important that the local (!), virtual drive letter, which is generated from the batch using the SUBST command, is entered with “Always with DBFNTX” in the ADS configuration. This is necessary because the local PC CADDIE will start from there, and this is also the location where a few database driver (ADS) functions will be executed - so you have to avoid the situation where the location is not found because the SYSTEM account does not detect user-related drives.