>Fox 7 exe running on an NT4 network. When 2nd user open same screen as another user, he/she gets "attempting to lock" message (although no one is editing). What do I have set wrong.
>
>Thanks, Randy

I know this is obvious, but do you attempt any physical locks when the form starts up? Are you creating views on the fly (ie. CREATE VIEW ...) because I think it locks the DBC.

Have you tried to trace it with a SET STEP ON? Sometimes that is hard to do if the error is occuring in the init of one of the form objects because there is no code to trace. However, if it doesn't blow up in the Form.Load but never makes it to the Init, then it probably is an object trying to init, like a rowsource problem. At that point I would try making a copy of the form, then have a second instance of your app instantiate that one. Remove objects one at a time (or possibly set the enabled to .F.) until the form does instantiate (sort of a divide and conquer method). It's slow but usually finds the offending object.