>How have you folks out there handled removing the VFP5 run-time engine and associated installed components from a user's machine AFTER you've upgraded your apps to VFP6 and redistributed the new VFP6 runtime engine? Or have you handled it at all?
>
>I mean, for those who've migrated a VFP5 application to VFP6, did you "clean up" and getting rid of the old VFP5 runtime engine and things that became obsolete? Did you programattically get rid of VFP500.DLL in favor of the new VFP6 run-time engine, VFP6R.DLL etc., etc.?
>
>I'm about to roll down that road and hadn't considered the housekeeping I might need to do. It's not like I want them to have to uninstall the old and install the new.

Like Evan, I didn't bother either. It doesn't cause any trouble, and eventually an OS upgrade will do the job.