>>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.
>
>You would think, but if VFP5 didn't recompile then the code would have run fine under VFP6 when re-run, instead of still giving NEWOBJECT.PRG errors...

You're most likely correct on that. The real gotcha with this can occur if you've used some of the functions that were in FOXTOOLS.FLL in VFP5, and are now part of regular VFP6. Tons of fun to be had dealing with that!