Cannot find database dll...

[Fursten]

Hi,

I´m using Crystal Reports 8.0 OCX and Visual Basic 6.0.
In the machine where I´m developing (win2000) I can preview and print reports without any problem. In other machines I can make it to (I only tried in win2000 machines...)

In the client... it doesn´t work!))

They all have winnt 4.0 machines with MDAC installed, thats why I can connect to the database without any problem. However, when I´m trying to preview and print a report (either based on a stored procedure or just by using linked tables inside the report) I get this error:

"Cannot find database dll"

In the reports I´m using the OLEDB driver. I already actualized this dll (because I had been getting another kind of error first...) to the 8.0 version (is name: p2soledb.dll). This was usuful in win2000 machines!

However, I started (not in win2000) getting that error I mentioned... I already installed in winnt directory the file: p2bbnd.dll as the crystal site told us to do, however that didn´t solved my problem...

Any ideias?

Thank you

Sergio Oliveira

 

[VaderTrader]

I've seen a similar issue when migrating a report that runs locally (on a Windows 2000 Professional machine against a SQL Server database) to a Citrix Server environment. The error message is usually "physical database not found"

I've found that copying all of the dll files from c:\winnt\crystal to c:\winnt\system32 (or equivalent) makes the report run. However, there is a risk that some other applications that use the Crystal runtime engine (crpe32.dll) may complain, so make sure you can track and delete the files if necessary.

 

[Guest_imported]

Hi,

I am a manager Server systems.
We operate a number of NT & MEtaframe-servers.
Some (Metaframe/Citrix) of them handle applications with crystal reports involved. I am not an expert on that, but already some years in the field. I ran into this problem with a new application. It had the same .....dll not found. error.

I used plain old logic; added the location from the crystal reports folder to the path-statement for all users. Reports went fine after that.