That answer is very correct as I had the same problem a few months ago -
the report worked on the development machine but not on the users
machine. Something I found useful back then was an application called
HandleX.exe that I found at www.sysinternals.com. Basically it is a Dll
viewer and allowed my to view all Dll's being used by any particular
application.
Using this I was able to find out what Dll's were being used by the
application on the development machine before and after the report
loaded and just sorted through those called for the report to see what
was not being installed on the user machines.
I have found this technique useful not just in sorting out this problem,
but has helped solve numerous problems where the user machine would get
a problem the development machine wouldn't.
Quote:
> I'm having some similar problems which are not solved so far.
> Somewhere it was written, that the pd*.dlls are 16 bit dlls and
> the p2*.dlls are the 32-bit dlls. The error messages of CR are not up to date
> and still use the 16-bit names.
> Try to find the p2bdao.dll and copy it on the clients.
> Martin
> see the thread Open CR7 at runtime: PDBDAO.dll missing (???!!!)
> > I am getting "PDBDAO.DLL not found" followed by "Physical database not
> > found." on installs (not developer machines), except for one machine which
> > works. Trouble is, nobody - developer or user - has the DLL, but it works
> > on some machines.
> > I will be much obliged for any insight.
> > Thanks,
> > Chase Saunders
> > Burgess Business Solutions
PDBDAO.DLL not found