We've recently had a problem when we try to register the 'CRAXDRT.dll' on a Windows 95 machine.
The client machine does not have Crystal Reports installed on it. Crystal Reports are being prepared and displayed through an application written in Delphi (making use of the CRViewer component for displaying the reports).
We make a habit of installing the 'CRAXDRT.dll' along with the 'CRVIEWER.dll' on each of the client machines. up until now we have not seen any problems with this - admittedly they have mainly been Windows NT or Windows 2000 workstations/servers.
When we run the commands (through a .bat file) :
C:\Windows\System\RegSvr32 Craxdrt.dll
C:\Windows\System\RegSvr32 CRViewer.dll
We get a successful registration message for the CRViewer.dll but a failure reported by RegSvr32 for the attempted registering of Craxdrt.dll
We've ruled out a damaged DLL and an incorrect path for the RegSvr32 (else the CRViewer.dll would fail to register also)
Someone suggested that we might be seeing this issue on the Windows 95 machines as they are an early release of the OS.
Would anyone know whether this might be a deciding factor ?
Can anyone suggest any alternate issues I've overlooked ?
Thanks in advance
Steve
The client machine does not have Crystal Reports installed on it. Crystal Reports are being prepared and displayed through an application written in Delphi (making use of the CRViewer component for displaying the reports).
We make a habit of installing the 'CRAXDRT.dll' along with the 'CRVIEWER.dll' on each of the client machines. up until now we have not seen any problems with this - admittedly they have mainly been Windows NT or Windows 2000 workstations/servers.
When we run the commands (through a .bat file) :
C:\Windows\System\RegSvr32 Craxdrt.dll
C:\Windows\System\RegSvr32 CRViewer.dll
We get a successful registration message for the CRViewer.dll but a failure reported by RegSvr32 for the attempted registering of Craxdrt.dll
We've ruled out a damaged DLL and an incorrect path for the RegSvr32 (else the CRViewer.dll would fail to register also)
Someone suggested that we might be seeing this issue on the Windows 95 machines as they are an early release of the OS.
Would anyone know whether this might be a deciding factor ?
Can anyone suggest any alternate issues I've overlooked ?
Thanks in advance
Steve