>Ed:
>I know that much of what we do is PFM (Pure ... Magic), but I agree that biting the bullet and re-compiling the 5.0 app gives a developer and their users a much better chance for a positive result and most anything else is just asking for trouble.

Great, but that doesn't cover the question; some of the functionality referenced in the runtime either is referenced by or relies on references from the registry related to COM, and that's why it's necessary to register these DLLs, in some cases use delayed copy and registration, and often necessary to add/update files that the runtimes depend on. It's a really disgustingly complex issue - just take a look at the VFP Runtime DLLs using the Dependency Walker sometime. If you play nice and do as MS suggests, using Setup Wizard (yeah, the versions that work) or the VSI with the VFP6 Merge Library, or carefully implement all the install requirements outlined in VFP6R.DEP, create the templated registry entries from the .REG that don't get built by self-registration, and ensure that all the little niceties of keeping your OS up-to-date (like making sure DCOM is installed on old Win95 and WinNT systems) then I wouldn't spend so much time answering "...but I copied the VFP Runtime files on the new machine and WAAAAH! my app fall down go boom! Did I err?"

I need more codeine, coffee, and perhaps a good, stiff drink...