>>Sounds like a hi-tech version of dll hell :).
>
>Actually it's not as long as you have a reasonably recent version of .NET installed. .NET 4.0 was a nightmare because they had 2 different versions that you couldn't easily tell apart.
>
>Sorted with .NET 4.5 and later which is forwards and backwards compatible.

I had the opposite problem last week. Running Crystal 10, for some reason we were trying to use xml as transport of data to report on, and then it tries to use crdb_adoplus.dll, which requires 2.0... which worked swimmingly here, but on the target machine there was no 2.0. Now the kicker is that it can run with 4.0 or later but you have to tell it in app.config, which doesn't exist in a vfp app using CR ActiveX. Luckily, this was just an attempt for a workaround - and then we solved the original problem so the workaround became unnecessary. Otherwise, I wonder whether there would be a solution at all. Googling it out didn't help, because all the solutions were for .net, if there was anything for ActiveX it was probably on page 43 and would work only on XP :).