Arthur,

If you are in mucking with a VCX by hand you had best know what you are doing if you expect it to work correctly. VFP depends on its reserved values to be what its code is expecting. I think the error you got is entirely possible depending on what VFP was trying to do with either too many or too few records of the file.

You should issue a COMPILE CLASSLIB after any manual work on the VCX.

Methods missing can indicate a failure to have the correct content in the methods memo and/or the reserved column that holds the names.

>I am in the middle of converting a financial app written in FPW26 to VFP8 under XP. I made my own library of form classes from the original screens and all that, but sometimes methods don't fire, and some classes even refused to instantiate, throwing up an error 46 dialog ("Expression evaluated to an illegal value").
>
>Through manual editing of individual objects from the class definition in the VCX (and learning along the way that the reserved2 field in the first record of the class definition contains an object count that MUST be updated!), I eventually isolated the cause of the error to something left over from the old screen, an entry calling a nonexistant function in the NumberofElements property of combo boxes.
>
>I would expect this to cause a "function not found," not "illegal value!"
>
>Has anyone else observed problems with VFP 8 returning an error that is less than accurate?