The following are some recommendations. For complete information,
you should consult with either your Windows Manuals or your hardware/network
consultant, or both.
- Share Your Server Drive Where You Install WinCargo Back End
- Map the Server Shared Drive to Each Client PC
- Install WinCargo Front End through Network
- Create WinCargo Program Group
- Create WinCargo.ini Icon
- Configure "WinCargo.ini"
- Keep the Latest Front End Programs As a Design-Master-Copy in a Sub Directory
- Printer Mapping
1. Share Your Server Drive Where You Install WinCargo Back End
 | From Server PC, click "My Computer" icon from desktop.
| Select the local drive, e.g. drive C, which you wish to share through the network.
| Click "File" menu and select "Sharing" menu item.
| In the "Properties" dialog box, select "Sharing" tab and click "Shared As" radio button.
| You can take the default "Share Name" and click "Ok" button.
| Optional: Alternatively you can share only "WinCargo" directory.
| | | | | |
Back to top
2. Map the Server Shared Drive to Each Client PC
| From Client PC, click "Network Neighborhood" icon from desktop.
| Double click the Server PC under "Entire Neighborhood".
| Select the Server's shared drive. Click "File" menu and select "Map Network Drive…" menu item.
| In the "Map Network Drive" dialog box, click "Drive" combo box and select a drive letter, recommended to "W" for "WinCargo" consistently for every Client PC throughout your network.
| Click "Ok" button.
| | | | |
Back to top
3. Install WinCargo Front End through Network (Optional)
You can install WinCargo front end through network much faster and more easily by doing the following:
| From Server PC, create a sub directory under "WinCargo", recommended "WcFEDisk".
| From under "WcFEDisk" directory, create sub directories, "Disk1", "Disk2", "DiskN", where "N" is the last diskette of your Client Diskette Set.
| Copy all files in Disk 1 of Client Diskette Set into "Disk1" sub directory.
| Do likewise for "Disk2" up to "DiskN".
| From each Client PC, run "W:\WinCargo\ WcFEDisk\ Disk1\Setup.exe". It will zip through as if you are installing from a CD.
| | | | |
Back to top
4. Create WinCargo Program Group (Optional)
It is recommended that you create a program Group for WinCargo.
| Run "Explorer"
| Open "Windows" folder and find "Start Menu" folder.
| Open "Start Menu" folder and find "Programs" folder.
| Open "Program" folder and find "WinCargo" folder.
| Select "WinCargo" folder and click "File" menu, then click "Create Shortcut".
| A new entry at the buttom, "Shortcut to WinCargo", will be created.
| Drag this entry onto desktop.
| | | | | | |
Back to top
5. Create WinCargo.ini Icon (Optional)
It is recommended that you create an Icon in "WinCargo" Program Group:
| From the "WinCargo" Program Group, click "File" menu and select "New" menu item.
| Click "Shortcut" to bring up "Create Shortcut" dialog box.
| In the "Command Line" text box, type in "C:\WinCargo.ini" and click "Next" button.
| In the "Select a name for the shortcut" text box, take the default "WinCargo.ini" and click "Finish" button.
| | | |
Back to top
6. Configure "WinCargo.ini"
It is recommended that you verify the following 2 lines in [Options] section:
[Run-Time Options]
...
[Libraries]
...
[Options]
...
SystemDB=W:\WinCargo\WCSYSTEM.MDA
BackEndDB=W:\WinCargo\WCB.MDB
...
(Where "W" is the networked drive Server is residing.)
Back to top
7. Keep the Latest Front End Programs As a Design-Master-Copy in a Sub Directory
It is recommended that you create a sub directory under server's WinCargo directory, e.g. "Program", to store WinCargo's two front end and one library programs - WinCargo.mdb, WcMntnc.mdb, SSLib.mda.
When you made some modification or received WinCargo's new version or patch, it will be handy just to tell the users to copy the whole directory to their own local WinCargo directory.
When upgrading to a new version, you can install the new front end diskette set in just one PC and copy only these three files to the "Program" Directory. Have the users copy over all the three files. Do not assume that the only file changed is
WinCargo.mdb.
Back to top
8. Printer Mapping
We saw many "intuitive" printer mapping that the locally hooked printer is mapped as default printer for that local PC, while all other networked printers as specific printers. This is not recommended.
We suggest that the laser printer (or the mostly used white paper tray) be mapped as default printer while all others as specific printers.
This way, you can define the printer destination for all the electronic forms and reports in just one design-master-database (please refer to item 7.)
and copy this original front end database to all the other clients. Remember this: the majority of WinCargo documents print to laser printer and therefore
it is not quite a good idea to define a dot matrix printer or the fax as default.
Back to top
|
