From: wog-NotThisBit-george@amd-p.com   
      
   "Dean Earley"  wrote in message   
   news:45893f79$0$2447$db0fefd9@news.zen.co.uk...   
   > Wog George wrote:   
   >> 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.   
   >>   
   >> Short of creating my own form and writing my own code to browse for a   
   >> file, can VB6 create a fully self-contained EXE that uses a common   
   >> control and can simply be run without the need for the program to be   
   >> installed?  It was suggested to me that VB6 was what I needed (was using   
   >> VB5 prior to now), so I bought an old copy of VB6 Enterprise especially   
   >> for the occasion.  Have I been misled?   
   >   
   > Common Controls is NOT the same as Common Dialogs.   
   > The file browse dialog is one of the latter and a LOT easier to create   
   > without the OCX than a common Control is.   
   >   
   > There are plenty of examples that use the Common Dialog API directly:   
   > http://www.google.com/search?hl=en&q=vb6+common+dialog+api   
   >   
   > Please note that any EXE created in VB6 still has a dependency on the VB6   
   > runtimes, but they exist on pretty much every computer now anyway (and are   
   > included by default on XP and above)   
   >   
   >   
   Thanks very much for that.  I'll give that a go and see where I end up.   
      
   --   
   George   
   "If I don't see you in the future, I'll see you in the past" - Tommy Bolin -   
   Melbourne 1975   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)