Renaming a data location
Follow these steps to rename a data location in FileCabinet CS.
- Choose , and select theData Locationstab.
- Highlight the data location in the list that you want to rename.
- Select theAdd/Modify Data Locationbutton.
- In theData Location Formatdialog, selectNext(theStandard formatoption is selected by default).
- In theAdd Data Locationdialog, choose the appropriate data location from drop-down list in theEnter the path of FileCabinet CS data locationfield.
- Update the text in theEnter an alias for this data locationfield as needed, and selectOK.
- SelectOKagain to close theSystem Configurationdialog.
Resetting data locations to default
FileCabinet CS stores data location paths in the
ZFCPATHS.DAT
file in X:\WinCSI\FcabSys
(where X is the drive FileCabinet CS is installed). You may need to rename the ZFCSPATHS.DAT
file if you receive a message that indicates the data location is unavailable even when the data location is mapped and accessible from your workstation.Renaming the
ZFCSPATHS.DAT
file removes all but the default data locations that have been set up in the System Configuration
dialog. No data is removed, but you are required to re-add any additional data locations that have been set up.Use the following steps to reset your FileCabinet CS data locations.
- Close FileCabinet CS on all workstations.
- Navigate toX:\WinCSI\FcabSys(where X is the drive FileCabinet CS is installed).
- Rename theZFCPATHS.DATfile toZFCPATHS.DAT.old
- Re-open FileCabinet CS.
- Choose and select theData Locationstab. The alias should now display as<default>and the data location path will be set back to the original installation location.noteIf this path is incorrect and you can open FileCabinet CS, select theAdd/Modify Data Locationbutton to add the correct data location.
- If you are still receiving an error message from a workstation, open FileCabinet CS from the server where it is installed. If you are able to open FileCabinet CS, add a data location, and then try to open FileCabinet CS from the workstation again.
If you're still receiving errors after following these steps, verify that the workstation has the correct permissions and drive mappings.