Error previewing report

[Strannik]

I use Crystal report component(crystl32.ocx) in the Visual Basic application(SQL Server database). On my side everything is OK. On the client side crystal report generates error: "Can't find database DLL". The only difference between our systems is that I have VB installed whereas he hasn't. Maybe somebody know the cause of the error or which exactly dll is required to preview report ?

 

[StevenK]

What database are you running your report against ?
I'd say the problem stems from the fact that you don't have the appropriate database DLL for the report running against the database backend.
These include dll's such as p2sodbc.dll, p2ssql.dll, etc (for a list please see the developers help files in the Seagate Software folder installed).
I hope that this helps.
Steve

 

[chelseatech]

As a general rule, I copy everything from WinNT\Crystal to the client PC. Also check that the ODBC name is set up and spellt correctly and they have the correct DB client installed. Editor and Publisher of Crystal Clear

http://www.chelseatech.co.nz/pubs.htm

 

[Strannik]

Sorry if I misunderstood something. I'm a beginner in Crystal Reports and never used it before.

To chelseatech:

True decision but I've found a lot of libraries in the specified folder and I doubt that all of them are required to run reports on the client's machine.

To StevenK:

Thanks, I've registered needed libraries and everything works. The original problem was to update a number of Crystal reports from 7 to 8.5 version. The DLL problem and a fact that I had to change DB driver/provider crushed me hard but I've made causes out.

 

[koukouroukou]

You realy need to copy the hole Crystal folder to clients winnt for later ploblems (beliave me) also copy to c:\winnt\system32 the rest

p2sodbc.dll
p2ssql.dll
ntwdblib.dll
pg32conv.dll
sscsdk80.dll

with both P2 dlls into system32 you will not have to change DB driver/provider of the report (strange but true). At my clients i am able to open both Direct SQL and ODbc driver reports and i have not created any file or System DSN to the clients (that really saved me cause otherwise i would have to convert 130 reports).

If you want to export reports or view Graphs there are more dlls that you will need.

 

[StevenK]

koukouroukou - I'm not sure the suggestion of copying the whole folder(s) to all client machines is a sensible one.
If we've been able to pinpoint those files as needed (from the Crystal Help files) then this should be sufficient - and this does appear to be the case.
Copying umpteen files within due cause may cause more problems than it solves.
If the majority of files are required due to the work being done on the client then rather than copy folders I'd certainly favour the idea of instally Crystal Reports as neccessary onto the client machine(s)
Steve

 

[koukouroukou]

StevenK you may be right but i did a lot of tests for previewing , exporting etc etc and my suggestion is full copy of this folder.Now i have managed to have a full client application with all the options i want and with no problems.