Hi all:
Our app ships with both 8.5 and 10.0 Crystal reports, and two custom dll's to fill them with fresh data.
We started with 8.5 only, but then started getting customer reports of conflicts with other apps that used 10.0 components. So we added the dual version support. We install version 10 dlls on Win2k and XP machines, and version 8.5 on Win9x and NT.
Now, of course, we are getting customer reports of conflicts with other apps that are running CR 8.0 or 8.5 components. These "bullying" apps install their dll's regardless of version issues - they overwrite (our) newer dll's with (their) older ones. (Our app runs fine until the customer installs the other app, which breaks our stuff).
Does anyone know of a way to "isolate" our CR 10 dlls? The primary file is craxdrt.dll - CR seems to have been rather cavalier when changing over from 8.5 to 9.0 with this dll - critical backward compatibility was simply left out or ignored. Can I just rename one version, say craxdrt10 for our version 10.o file, and register it? Any ideas how to test such a solution (we do have a test rack available, with baseline images that can be restored after we melt the computer down with not-ready-for-primetime installation attempts!).
Thanks in advance,
Dan
Dan Walter
Daniel.Walter@uvm.edu
try { succeed(); } catch(E) { tryAgain(); } finally { rtfm(); }
Our app ships with both 8.5 and 10.0 Crystal reports, and two custom dll's to fill them with fresh data.
We started with 8.5 only, but then started getting customer reports of conflicts with other apps that used 10.0 components. So we added the dual version support. We install version 10 dlls on Win2k and XP machines, and version 8.5 on Win9x and NT.
Now, of course, we are getting customer reports of conflicts with other apps that are running CR 8.0 or 8.5 components. These "bullying" apps install their dll's regardless of version issues - they overwrite (our) newer dll's with (their) older ones. (Our app runs fine until the customer installs the other app, which breaks our stuff).
Does anyone know of a way to "isolate" our CR 10 dlls? The primary file is craxdrt.dll - CR seems to have been rather cavalier when changing over from 8.5 to 9.0 with this dll - critical backward compatibility was simply left out or ignored. Can I just rename one version, say craxdrt10 for our version 10.o file, and register it? Any ideas how to test such a solution (we do have a test rack available, with baseline images that can be restored after we melt the computer down with not-ready-for-primetime installation attempts!).
Thanks in advance,
Dan
Dan Walter
Daniel.Walter@uvm.edu
try { succeed(); } catch(E) { tryAgain(); } finally { rtfm(); }
