This turned out to be much more insidious than I would have thought.

Here's what happened:

Someone went and ran the application interactively under VFP5. VFP5 appeared to realize that the compiled code it was running was no good, and recompiled whatever it came across. Of course, it bombed pretty quickly, with errors like the aforementioned NEWOBJECT.PRG not found.

Then, the application was run interactively under VFP6. Well, VFP6 did NOT concern itself with the fact that the code it was running had been compiled under VFP5. Therefore, the compiled code obviously contained some instructions that told VFP to go looking for NEWOBJECT externally, as it would have have to have been in VFP5! So even in VFP6, NEWOBJECT.PRG not found kept appearing!

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...

Thanks everyone for your help.

Eric



>>Roxanne,
>>
>>Actually I already tried that (forgot to mention it in the post), to no avail. But thanks. I'm figuring the same thing, but I am holding out hope that someone will have some across this before...
>>
>>>Sounds like you could re-apply service pack 3 (or 4) for VFP6 and that might fix you up. When runtimes get crossed between versions, your pretty much guaranteed to have to do the reinstall dance to get it all better again. Good Luck!
>
>Eric,
>
>You'll probably have to go through the whole song-and-dance:
>
>Install VFP5
>Install VS97SP3
>Install VFP6
>Install VS6SP3/4