>>>If this is on a network, check to see that all your users are not using the same resource file. This could cause the lock problem. You may be accessing the resource file at startup but setting resource to off later in your app. Some times two users could come on at the same time and get a conflict when they try to access the resource file (foxuser.dbf) at the same time.
>>
>>
>>I have a few small apps that use foxpro and the foxuser.dbf file. Each one has that same copy in their own directory. Also I have some reports that run inside
>>the main application and some that access those tables but run outside
>>of the main application. All these reports are in the same directory
>>and there is a copy of the foxuser.dbf in that directory as well as in the main directory of the main application.
>>
>>Do you think this may be causing a conflict with the main application that is producing the error messages?
>>
>>If this is so, would it be best to use the set command in the autoexec.bat
>>to find the resouces in the same place rather than have multiple copies on the
>>system? "Set FoxProW=p:\psmain"
>
>My applications all start from a config.fpw, inside that config file I set resource off. This is how I do it, it may not be what you
>need, but I have found that if I need a resource file inside my application I declare it there with the command
>SET RESOURCE TO filename and the SET RESOURCE To and SET RESOURCE OFF when that appilcation is done. I also ensure that the resource file residing on the network is set to READ ONLY. I do not user the foxuser file at all.

Andy, double-check that ALL your 'outside' programs have SET Exclusive OFF.

HTH
Barbara