>Fred,
>
>Thanks for the response...
>
>>I wouldn't call it "random", but it more than likely has to do with a caching issue. If you do have the two projects open at once, you very well might be causing your problems. I've seen it with classes that are named the same, but stored in differenct .VCX files between the different projects.
>
>You are right, it isn't random, but I have yet to figure out the exact thing that triggers it...
>
>>About the only real solution I was able to come up with, was not to open the differrnt projects in the same instance of the VFP IDE. If you really need to work on two different projects, open a separate copy of VFP IDE for each one.
>
>Today I have had it happen twice without opening the project that uses that bad VCX name getting inserted into Classloc in other words, no two-projects-open-at-once). So, I am going to start digging through code to make sure there are no dirty tricks in there (this is an inherited project...I just started at my new job). Maybe I can see where heavy-duty class operations are going on and try to pinpoint that? *shrug* I really don't know where to start, and it is very annoying. Especially when the CEO steps in for a demo and when I load my form, BLAMMO! I get a class not found error... *sigh*

It may not have to have both projects open to occur. If you ever HAD both projects open, the other form's use of the class from the wrong project could already have happened. Once that's happened, the classes are cached, and can further effect what's happening. It drove me crazy until I just cleaned up all the forms, and then started using the 2 copies of the VFP IDE.


>
>Has this bug been reproduced and documented for the Fox team? Even with having multiple projects open, there is no excuse for VCXes exchanging information...

I could never "produce it on demand", but it certainly wasn't from lack of trying!