@Thierry: With Sysinternals Process Explorer you can find which VFP session is using this VCX (just search with the library name)

@Rick: Presumably you are not using FoxBin2Prg with your Source Control, because if you do, then you shouldn't have those problems with SCX/VCX binaries because some types of duplicity on internal classes are detected and corrected, and, on the other hand, FoxBin makes VFP 9 Source Control no more "bloody hassle" as you describe. Some Develope Teams sharing and modifying same components (VCX and SCX too) concurrently can tell you about this. ;-)


>I've also had an interesting issue recently where FoxPro somehow managed to create multiple instances of the same class in the same VCX file. Saving would sometimes work, sometimes not as saves would write to various random versions in the file.
>
>The whole VCX/SCX system was a cruel joke by the FoxPro team on us :-) So many possibilities for corruption not to mention all the bloody hassles related to managing source control. But for visual components unfortunately there's no other choice.
>
>+++ Rick ---
>