I did use filemon program and again all necessary dll and bpl were installed. So I went back to development machine after starting d7 I renamed the D7 bin directory to BIN1. I now tried to run myapp under the IDE and got the message I was trying to use a feature that was on the CD or needed to be on the HD.
So I created a new project directory and built my main form. Then I started importing panels one at a time compiling and attempting to run under IDE till finally I found the offending panel. I could see no obvious reason for the offense. Panel contained basic object edit boxes, memo fields, drop down , datetimepicker, labels and buttons thats all. So after creating the offending panel completely new with new panel and same objects problem went away. Thanks for all your responses. Just wish I knew what caused the problem so I can avoid it in the future. Tony ----- Original Message ---- From: David Smith <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, November 29, 2007 2:05:47 PM Subject: Re: [delphi-en] Required DLL / packages for application Are you telling your app to look in windows and windows/system32? dave Tony Taylor <[EMAIL PROTECTED] com> wrote: When I install my app on a fresh pc if gives me a fault address error. I looked under view debug window modules and check every dll and package shown there and they all exist on fresh pc. I loaded D7 on fresh pc and app runs - uninstall D7 and app gives fault error again. I am trying to find what I am not installing because what ever it is it gets install when I load D7. I am using firebird and firebird odbc they are both install and running. Tony ----- Original Message ---- From: Rob Kennedy <[EMAIL PROTECTED] wisc.edu> To: [EMAIL PROTECTED] ps.com Sent: Thursday, November 29, 2007 10:50:09 AM Subject: Re: [delphi-en] Required DLL / packages for application Glenn B. Lawler wrote: > Tony, > >> Several years ago I either compiled a certain way or ran the app a >> certain way and I was able to see all packages and dlls my appp called >> during execution. Could someone refresh my memory on how to do that. > > There are probably a number of ways to do this. The Windows add-in called > "Quick View" shows all the DLLs used by any application. If it is installed, > a menu selection appears in the popup menu in Explorer when you right- > click on an executable file. Quick View hasn't been included with Windows for many years; I think Windows 98 was the last one. Tdump will show you the same information as Quick View. But neither shows which DLL are called at run time. They only show which DLLs the EXE links to at load time. It doesn't show which functions are actually called on any given run, and it doesn't show which DLLs are loaded at run time with LoadLibrary. I'm not aware of anything that will do that, although wouldn't be surprised if some tool from Sysinternals provided something like that. Tony, what are you looking to do with this information? There might be other ways. -- Rob ____________ _________ _________ _________ _________ _________ _ Never miss a thing. Make Yahoo your home page. http://www.yahoo. com/r/hs [Non-text portions of this message have been removed] ------------ --------- --------- --- Get easy, one-click access to your favorites. Make Yahoo! your homepage. [Non-text portions of this message have been removed] ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping [Non-text portions of this message have been removed]
