Hi Rober,

>>
>>That's interesting...the syntax for the loading of the form is just simply
>>
>>DO FORM ArPay NAME oArFrmPay LINKED
>>
>>I've rebuilt the form many times, and have tried saving it as a class and doing the old...
>>oArFrmPay = CREATEOBJECT('ArPay')
>>oArFrmPay.SHOW()
>>
>>No macros or anything like that. I could load it 100 times over the course of a day, and 3 times it might give me a syntax error on the DO FORM or CREATEOBJECT() line.
>>
>>The failure on the local view is interesting.
>>
>>I do have an error handler that catches it, but (unfortunately) when I take the user back to the main menu to retry, it happens again. If they exit the app and re-enter, it works fine.
>>
>>Thanks,
>>Keivn
>
>
>Is this a multi-user app? What you might be getting is a misreported "Database object is being used by someone else. (Error 1709)" - you'll sometimes get this if two (or more) users attempt to open the form at the same time: what's more it won't always report 1709 (my VFP5a likes to report error 2200 whatever that is).
>
>Just a thought

It is definately a multi-user app. I have a built-in trap/retry for Error 1709 (as well as 3, 108, 109, 1502, and 1995). I've never seen Error 2200 though. Interesting thought.