Paul,
I don't think it will affect it but I could be wrong. From what Trey posted, this corrected the same error on a system he worked on. And you may need it to be higher anyway for other things you want to do down the road.

>Larry,
>
>They are running Windows98 on the workstations. The server is a dedicated server. You are thinking I shouldn't change the Maximum Locks per Connection? I'm not sure what else to try. He is supposed to be calling me back after he determines how to check that setting.
>
>>Paul,
>>This should work as it is running Novell not DOS as the operating system. Novell just looks like DOS.
>>
>>I don't think the Maximum Locks per Connection needs to be changed unless you are having problems on the server locking records. I remember creating an application installed on a Novell 3.12 server that had the functionality to track user logins. Whenever a user logged in, their record was locked in the users table. To determine who was logged in, an administrator would run a process that attempted to lock all the records in the table. If it couldn't get a lock, it assumed that user was already in. When the user base got over 600, it threw an error in the system (don't remember what it was) because it exceeded the locks per connection. This was increased on the server and all was fine.
>>
>>What version of Windows are the workstation machines running?
>>
>>*snip*