Relocating and maintaining an up to date case database is critical in multiple access installations, and it is important for users to understand exactly how path information is stored within a case database to prevent duplication and "lost" items.
The Sanction II subdirectory structure is fixed within the program to follow certain rules and look for certain data based on specific locations. These locations are recorded in the case database file.
To avoid case duplication, it is strongly recommend that anytime you move a case, you "cut" and "paste" the entire case subdirectory. If you "copy" a case and fail to update all of the current user's case paths, you may end up with duplicate cases.
File Paths
The most import thing to remember when moving cases and case items to and from the network is maintaining the correct file path information in the case database. If you move items and fail to update the database with the new path information, you may receive a "File not found" error every time you click on an item. By looking at the path indicated, you can usually determine what the problem is.
There are a couple of ways to insure that moving items around does not result in a loss of correct path information. The simplest is to maintain identical subdirectory structures on all machines or network drives used with the case.
For example, the Sanction II installation program installs Sanction II to the Program Files subdirectory by default. If all of your users use the same installation path, and you place network cases in an identical directory (i.e. Program Files\Sanction II) off of the root network drive, you will never have to worry about relocating items to the wrong file path.
Even if users have multiple drive mappings, the following drives would still be able to locate case items:
D:\Program Files\Sanction II\Cases
E:\Program Files\Sanction II\Cases
G:\Program Files\Sanction II\Cases
Z:\Program Files\Sanction II\Cases
since they all maintain the same directory structure. Any Scans or Case Items will all be placed in the appropriate subdirectories off of the Case subdirectory.
This is the simplest solution, but may not be suitable for network managers who maintain a strict network directory structure.
Alternate Method
If the network manager has provided only a single specific location for network cases, then if at all possible create the Cases subdirectory off of the root network drive. For example, if the network manager has allocated space on the F: drive, create the shared case directory as "F:\Cases". By using \Cases as the root, when you use the Relocate function, you can simply add any additional required path to this subdirectory (typically \Program Files\Sanction II, since the relocation destination is typically a stand alone) so that the Laptop or court PC will have correct path information.