Q: Can I use Ledger Management version 3 on the network?

A: Yes, all new 32-bit PDS programs will be network compatible.

However, there are some steps our users have reported that will lead to a better experience.

The links below will take you out of the PDS Web Site. These links are provided as a convenience. PDS is not responsible for the accuracy of the information.

1. Ensure you have the latest operating system and network driver updates for the server. Visit http://windowsupdate.microsoft.com/
2. Ensure you have the latest operating system and network driver updates for all workstations. Visit http://windowsupdate.microsoft.com/
3. Create (and share) a folder on the server BEFORE you setup either the server or the workstations. Know the UNC path to the shared folder. For example: \\Servername\PDSLed3 This is the path to the folder as explored through Network Neighborhood or My Network Places. Tip: Navigate to the folder and copy (CTRL+C) the UNC path from the address bar so you can paste it (CTRL+V) as the Database Destination during setup.
4. If you are using Windows XP Home or Windows XP Professional in a Workgroup Environment, disable Simple File Sharing. From Windows Explorer, select Tools, Folder Options, on the View Tab, scroll down and uncheck the option for (Use Simple File Sharing (Recommended)).
5. Grant full access to the network share to all authorized users. If you want control of what users can and cannot do, setup Users and Passwords within the program. At the network level, users need read, write, create, delete, (i.e. full control) over the complete share and all associated sub-folders.
6. When you setup the programs, use the UNC path (from step 3) to the database. Use the same UNC path to the database when running Setup on all workstations. Use the Same UNC path to the database if you run setup on the Server.
7. On the Server and all Clients disable Opportunistic Locking (or File Caching).
8. Double check that you are using the EXACT SAME path to the database for each installation. For example: Windows may see C:\PDSLed~1 and C:\PDSLedger as the same path, but not all servers will.
9. If the program produces errors after changing the database path, close the program and use windows explorer to delete all *.lck and *.net files within any program sub folders.

Please review the Installation Checklist to help you plan the installation of the program on your network.

You will need Adobe Acrobat Reader to view the document.

Opportunistic Locking - Windows

For Windows 2000, XP, and 2003 see Microsoft Knowledge Base Article 296264
http://support.microsoft.com/default.aspx?scid=kb;en-us;296264

For Windows NT see Microsoft Knowledge Base Article 129202
http://support.microsoft.com/default.aspx?scid=kb;en-us;129202

Opportunistic Locking - Novell

Some versions of Novell refer to Opportunistic Locking as File Caching.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10071902.htm

From the Novell Technical Information Document:
File Caching and Opportunistic Locking - TID10071902

To disable op-locking in the client, then perform the following

1. On Windows 9x workstations go to the advanced client settings and turn off the setting for op-locking.
2. On Windows NT/2000/XP workstations go to the advanced client settings and turn off the setting for File Caching.

Also a new feature in NetWare 5 SP5 or greater allows us to turn off op-locking at the server console.
?set client file caching enabled = on/off?

Back to Ledger FAQ Page