The environment object sets exclusive off and any forms with data environments are used with private datasessions as rule here, unless there is some special case. In this case, there was no error. It just simply did not open or the open dialog box would appear. Now the problem has gone away since I took any framework based dev directory off source control with Visual SourceSafe. I, perhaps clumsily, put the projects under source control with the shared db included. It is confusing though, because I would think if this was a problem, the first app would not be able to use the db either. ie set to readonly? But you can still open a table that is read only, but not edit. Same is true for a database. Now that source control is turned off (with no other changes) I can happily cruise along in any app and open and close forms using the same tables to my heart's content. Incedentally, the cure didn't take place until the VSS projects were deleted. Maybe there is something else I'm overlooking?

Eric K.


>Yup, I'm sure. You can try it with a base class form, or more easily, check out the docs on SET EXCLUSIVE
>
>>I think we're in agreement that the tables are being opened exclusively, somehow, though.
>
>I have no idea how much experience Eric has deciphering error messages, I just wanted to make sure that we are all on the same page...