> Suppose I have opened two projects A and B, and these two both have a
> Product class but are in two different VCX files and that the both their
> Product classes have the same method name say Update(). Sometimes, VFP
> would save the Product.Update method code belonging to project A to B!

That is absolutely evil, and I guess this can cause resultant app bugs that are most difficult to track down. Have you been able to repro this or is it one of those Heisenbugs that pick some inopportune time to strike and then go into hiding?

Our coding rules forbid that any two classes within the same environment have the same name (because of Fox's internal class caching) and this may be the reason that we have not encountered the problem yet.