On Mon, 30 Apr 2018, at 4:00 PM, Chris Davis wrote:
So possibly if a VFP9 app was installed, and then a VFP7 app was installed after it some older files might get replaced which could generate a class not found in the VFP9 app ? Sound reasonable?
Don't think so because the VFP runtimes have different names - VFP9R.DLL, VFP8R.DLL and so on.
More likely an EXE or APP built with VFP9 that you are trying to execute under an earlier version.