>>>It's not enough to declare that version isn't a problem. Please explain how would you handle VFP9 and VFP9SP1 runtimes in this scenario. IOW, what if your application requires VFP9 and mine on the same computer requires VFP9SP1. How that would work?
><<
>
>Ok, let´s begin to patch this puzzle and really differentiate versions and not make it a semi-secret and name it what it is:
>VFP91R.DLL or VFP9SP1R.DLL
>
>This would obviously break the 8.3 naming scheme of the runtime res files, but I do hope that won´t break VFP. ;-)
>

That's not how VFP works right now and it's not going to change soon if ever. I still waiting for you explanation why the runtime versions aren't the problem in the scenario I outlined.