Technical Considerations

If you have only one computer running Lynx, then there are no network or other technical considerations to worry much about. However, if you have two or more computers hooked together in a network, then a number of very significant issues need to be addressed. These tend to get rather technical, but they're essential to good performance of the system.

Columbus Systems is primarily a software company, not a hardware or network business per se. However, we will help you with this as much as we can. 

If you have an internal network of several computers with relatively heavy usage, you should seriously consider finding a local technical consultant who would be available on-site to help you deal with these kind of considerations.  


Network considerations . . .

1. Do NOT use a peer-to-peer network.  It's not that this approach won't work . . . it's just that our experience has shown that a peer-to-peer approach will not give you the performance you want. 

2. Instead, use a Microsoft Windows NT (release 4.0 or later) or Windows 2000 client-server network. 

3. Your data and the Lynx executable code should be placed on the server.

4. Each client machine should have a shortcut pointing to the Lynx executable code on the server.

5. There should only be one copy of the Lynx executable on the network and this should be on the server.  All other copies should be removed.

6. The backup device (usually a Zip drive or a Jaz drive) should be physically attached to the server.

7. Every machine (including both the server and each of the client machines) should have a modem and a copy of the pcANYWHERE software.  If you don't have each of your machines set up like this, then Columbus Systems will not be able to directly support them.

8. The UserData alias on every client machine should point to the same place on the server.



Desktop shortcuts . . .

1. For desktop shortcuts, use UNC paths, like this:

The following BDE Administrator settings need to be made. To get to the BDE Administrator, do the following:
1. Left-click on the Windows button, then left-click on Settings, then on Control Panel. This will display the Windows Control Panel.
2. Double-left-click on the icon which will display the BDE Administrator window where these settings are made.



BDE Administrator Database settings . . .

1. Important: Use UNC (Universal Naming Convention) path names for aliases and BDE paths.

2. Set the PATH parameter of the USERDATA alias like this: 


3. The LocalData alias PATH should point to the local hard drive on each of the client machines, like this:


4. Set ENABLE BCD to TRUE, like this: 


BDE Administrator Configuration settings . . .

1. Important: Use UNC (Universal Naming Convention) path names for aliases and BDE paths.

2. Set the NET DIR path like this:


3. Set the BLOCK SIZE to 32768, like this:


4. Set the FILL FACTOR to 1, like this:


5. Set the Paradox LEVEL setting to 7, like this:


6. Set the BDE LOCAL SHARE property to TRUE, like this: