>>>Thanks but it's a no-go. :( In both cases, we have to compile a 32 bit version (with the path there) and a 64 bit version (with the x86 path there) for this to work. don't want two separate exes... and if the path doesn't exist at build time (which it won't on a build server), then it won't work for either :(
>>>
>>
>>>>>Any ideas?
>>
>>Wild shot;
>>Make subclass for 64bit version with no other then that required path change ?
>
>Checking on that one - not sure it works with the IMPLEMENTS statement but will definitely test...


Oh, I think it will work - provided you install the dll on both places on the build server. At run time you will have to decide which class to use

But then what do you do if the user installed it in another place - installers give the possibility where you want to install

Another possibility that comes to mind is ... at run time
(1) find where it is installed
(2) make a prog that targets the IMPLEMENTS to the right place
(3) Compile it
(4) Then use it