Hi,

Really is odd though... the four forms all were based on my dataentry form class... my app object runs a menu that has options to open those 4 forms. I then intentionally opened another VFP instance and opened the tables concerned exclusively. Now, when I go back to my original VFP instance and chose to run the form this error 2005 comes up.

Let's say Form A opens Table A and so on. Everytime I open Table X exclusively in another instance, running Form X would generate 2005! IF I close Table X which was opened exclusively, Form X would then run OK...



>>Well, I found out that if the table or tables in the dataenvironment have been opened EXCLUSIVELY somewhere else, then Error 2005 occurs!
>>
>>Is this what Error 2005 is? If so, how could I trap it?
>
>Nah, 2005 is something you usually get when you try to assign a value of a wrong type to a base-level property, or an impossible value - but mostly you get 1881 ir 1732; you may even get a 46 (just try to assign .textbox.taborder=32342).
>I've never really had a 2005, that really sounds like it's catching the few cases not covered by these three.
>
>Anyway, I'm not sure catching the situation when someone's got your tables open exclusively is high on anyone's priority lists. You assume the user has a config.fpw where exclusive=on, and that the user is likely to run the app twice (or have more users on the network) - but then you're dealing with the power user who can wreak havoc to your app anyway. Or you're assuming your user has VFP installed and is likely to open the tables from VFP - that's another power user you can't do much against.
>
>The actual solution would be to hand this error to your general error handler to log it, and quit the app gracefully. If someone else has a table open exclusively, there's not much else you can do, anyway.