>I don't know anything about it, but I've seen it too. I didn't put together that that is what was happening until just now...
>Usually you can't modify the class when someone even has an instanciation of it open (like modifying a form that contains on object based on the class), but I have observed really strange behavior: Sometimes I am able to open the class for modification but the method code is all gone. Immediately close and try to edit again, and access is denied.

Yes, that's what we've seen here, toolbar pictures missing, method code gone...

>When a class disappears from one of our libraries, it only disappears on one workstation. It is usually enough to CLOSE ALL and then open the library or project again, and Voila, the class has reappeared.

That's probably the same effect we get by removing from project, then adding back...

>You stated that more than one person is able to modify the class at one time, we have not found this to be true. If I need to modify a class that someone else is using, I do it in table form, or with the SuperClass utility.

I meant only one person actually editing one class at a time...a second could open the library/class (without everything appearing), and begin to edit, but will not be able to save if another person has class open. We haven't tried a save on the "blank" version after other person has closed library, would there be an overwrite of all good method code? (Hope answer's no :))

Anyway, I wonder what the logic is for allowing "shared" use? My thinking is that allowing multiple opens of a library is a good idea, but multiple opens of a class is probably not by design...this must be difficult to control, though, since it amounts to record-locking of the vcx...