I made the move a week or so ago to break up the folder locations, cleaned up the good vcx to the new location packed etc. I was hoping that by moving to a new folder this would either stop the problem or reveal something.

No Bueno. No change.

It just flips to the bad parent for no reason intermittently.

I can go for a day without a problem or I can have it happen 4 times a day for no rhyme or reason that I can see.

I just checked all relative paths. The are all relative

I am going to try changing the folder structure again.

I.E.
Bad
..\..\Common30\Libs

Current Good
..\..\Common30\ClassLibs

New Good
..\..\Classlibs

I am going to change parent class names

I.E.

Bad Parent
cForms.cBizObjForm

CurrentParent
BaseForms.cBizObjForm

change to
BaseForms.cBaseBBizObjForm

If this does not work and there are no more ideas here and I call microsoft and the problem resolves to CodeBook Framework then I am going to Impersonate Griver, lie about our ages, join the army as an infantryman
doing land mine cleanup. (I did not write this in codebook I am following behind).



>Ron,
>
>>The code is all on a single drive however I moved the parent classes to different folders
>>
>>s:\common30\libs && Bad Parent
>>s:\sommon30\classlibs && desired parent
>
>If you moved the classlib out from under the forms and classlibs then you are going to have to go in and repair all of the classloc columns as appropriate (make at leaset two independent backups first). VFP is finding the bad parent classlib by relative path or explicit path during the build process because that's what you told it to do. If you really want to find the problem classes rename the classlib in s:\common30\libs this will caue the build process to throw errors because the file can no longer be found.