dll h*ll

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

How can I find out (trace) what dlls are being called in my product?

I am trying to produce a crystal report from a commercial product that calls
some basic crystal dlls. On my own machine, on which I have installed a
licensed version of crystal designer, I have no problem. Theoretically, I
should be able to install the pertinent dlls on another machine (without a
licensed version of crystal) and be able to produce the crystal report from
the product. This machine must be missing some MS or other dll that the
crystal dlls need because it does not produce the crystal report.
Unfortunately, this failure to produce a report does not "raise" an error.
If I can just see what dlls are being called, I can copy them from my own
computer.

thanks, thanks, thanks,
 
Kristin said:
How can I find out (trace) what dlls are being called in my product?

I am trying to produce a crystal report from a commercial product that
calls
some basic crystal dlls. On my own machine, on which I have installed a
licensed version of crystal designer, I have no problem. Theoretically, I
should be able to install the pertinent dlls on another machine (without a
licensed version of crystal) and be able to produce the crystal report
from
the product. This machine must be missing some MS or other dll that the
crystal dlls need because it does not produce the crystal report.
Unfortunately, this failure to produce a report does not "raise" an error.
If I can just see what dlls are being called, I can copy them from my own
computer.

thanks, thanks, thanks,
Click to expand...

Use filemon with a filter on the name of your executable
http://www.sysinternals.com/Utilities/Filemon.html

Jon
 
Back
Top