From: dean.earley@icode.co.uk   
      
   > news:6b9ih.10947$HU.2692@news-server.bigpond.net.au...   
   >> I need to create an EXE that is truly "standalone".  By that, I   
   >> mean the executable file is all that's required for the application   
   >>  to run. My app has a button that fires up a common control (to   
   >> select a file), and this seems to be my stumbling block.  When I   
   >> try to run my program on another machine, it complains that   
   >> comdlg32.ocx is not registered properly.   
   >   
   > yes there is actually, when you use the package and deployment wizard   
   >  you can add files like comdlg32.ocx to the package so that when the   
   > application is installed all relevant ocx and dll files are installed   
   >  on the client machine as well. alternately, if the destination   
   > machine also has the VB6 runtime libraries on it, then you can just   
   > port the EXE and it will work fine because all the OCX and DLL files   
   > would already be on the machine.   
      
   That OCX file mentioned is not a standard VB runtime and is NOT   
   guaranteed to be installed in any circumstance.   
      
   --   
   Dean Earley (dean.earley@icode.co.uk)   
   i-Catcher Development Team   
      
   iCode Systems   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)