Basically, as long as the individual workstations share a .NET file on the network server, then they can coedit data tables. There are some BDE settings to be checked and possibly changed, and you will need to alter aliases to reflect the new location(s) of your data.
Here's a quick and dirty example: You have an address book with one table on a standalone machine that you want to make networkable.
1. Create a directory on your network where the table can be moved. Make sure all workstations can see it and have full access rights to it. Map a network drive to it and assign the same letter to each workstation (drive letters are important to Paradox).
2. Copy the table (and forms, reports, etc..., if you like) to the directory.
3. Open the BDE administrator on each workstation and set the NetFile location to the directory you created on the network.
4. Open Paradox and change any aliases to reflect the new drive letter/location of the data.
5. Turn off opportunistic locking on the server and write behind caching on the workstations.
6. Launch your application normally and go to work. If you've moved your forms to the network, then adjust your links to point there.
7. Check for performance issues and adjust the BDE settings as needed.