>After realizing this, the simple answer (which fixed the problem) was to recompile all files in the application under VFP6. This fixed the problem. But I am REALLY surprised that VFP6 did not automatically recompile everything itself on the fly. I can only figure that since the assumption is that VFP5 code will run properly in VFP6, there is no reason to recompile. But still...

Yep, that's why. VFP5 code runs fine in VFP6. Not sure why VFP5 would automatically recompile VFP6 code, though, but it probably just couldn't find the reference to NEWOBJECT and did not actually recompile it.