>>>>Sylvain,
>>>>
>>>>I am out of the office at a conference now so I can't test what you have said. I have SET EXCLUSIVE OFF where I set up the application environment before I load any forms. I shouldn't need to do it again should I?
>>>>
>>>>
>>>>>Try inserting this line in the DataEnvironment BeforeOpenTables() event:
>>>>>
>>>>>SET EXCLUSIVE OFF
>>>>>
>>>>>HTH

---

>Thanks for the reply Sylvain. The offending form has nothing in the Load() event. In the dataenvironment I have 12 tables, no methods, and AutoOpenTable and AutoCloseTable is set to .t.
>>>
>>>If your forms use Private Datasessions, then yes, you'll need to do it in the Load method of each form. It's best if you put that in your base-class form's Load method.
>>
>>Fred,
>>
>>I didn't realise but I do have SET EXCLUSIVE OFF in my base-class form's load method, and yet I am still getting this same error. I use default data sessions as well. I am now getting a bit frustrated with this problem. Any more ideas would be greatly appreciated.
>>
>>Thanks, Peter
>
>Which forms are getting the error? The Private Datasession forms, or the Default Datasession forms? If it's the Default sessions, you still need to have a SET EXCLUSIVE OFF somewhere in your main startup code for your app (or even EXCLUSIVE=OFF in your CONFIG.FPW). Maybe you should check what your current setting for EXCLUSIVE is in the debugger (SET('EXCLUSIVE')).

Fred,

Thanks for the reply. Well, I have learned a bit more. Set Exclusive is set to OFF everywhere. And I am only using Default Datasessions for all these forms in question.

What I have learned is that the Load event gets executed for the called form, but the Attempting to Lock occurs when running the Init event. The first line in the Init even is the PARAMETERS statement, since this form is called with a DO ... WITH command (a leftover from my Clipper days). It cannot get past the PARAMETERS statement. Are you aware of any problem here?

Thanks, Peter