Results 1 to 4 of 4
  1. #1
    Lounger
    Join Date
    Mar 2002
    Location
    Australia
    Posts
    42
    Thanks
    0
    Thanked 0 Times in 0 Posts

    run VB6 exe files in non-VB environment (VB6.0)

    It seems in theory VB exe file can run within any windows platform, only extra requirement is to install msvbvm60.dll file in the windows system folder. However, my VB6 .exe files can now run in windows which have installed VB6 without any problem but cannot run in other window platforms. The programs includes many ADO links between data forms and database. Any one gets a clue? Do I have to use Package and Deployment way to pack the program to run on other windows platforms (which i found is not convenient and too big to make withuot a CD burner ).

    David

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: run VB6 exe files in non-VB environment (VB6.0)

    You have to install the VB runtime for the executable to run unless the runtime is already there or VB6 is installed ... in which case, the runtime files are there. If you try to put the EXE on a machine with Office 97 on it, for instance, it won't work because that version was based on VB5. The PDW is the only way to insure that you have the necessary files to support your executable unless you have another installer like InstallShield or Wise. This is the ugly reality that gives the lie to the claim that VB executables have a small footprint. That *is* true of the executable itself but not of the runtime files needed to make it work. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  3. #3
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: run VB6 exe files in non-VB environment (VB6.0)

    There was a thread recently (here maybe, or in Word) about sniffing the References collection for any required libraries that are missing on the target platform. The code was not performing properly, but as a step in making your application more self-documenting, you could try having it first check to see if all the needed libraries are available on the target machine and, if not, popping up a dialog for your reference in supplying the needed items.

    From your description, the first place to look is ActiveX custom controls on your UserForms. Unless these are controls that come with Windows, then probably you will need to package and deploy them, as only developers have them by default.

    As for ADO, you can only count on ADO 2.1 on an Office 2000/Win 98 machine, and ADO 2.5 on a Windows 2000 or Office XP/Win98 machine. (See MDAC Release Manifests, ACC2000: List of ODBC Drivers Installed by Access, Office, and MDAC (Q208689) and OFFXP: Description of the System Files Update (Q286399)).

  4. #4
    Lounger
    Join Date
    Mar 2002
    Location
    Australia
    Posts
    42
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: run VB6 exe files in non-VB environment (VB6.0)

    Thanks for both replies of the hosts.
    I have used P&D method. One minor problem I havent worked out is: after install the package in a non-VB machine, I use Star|Programs|ApplicatioName to start the application. but it always firstly shows "Missing Shortcut" box and the Window searching animation icon is on to do endless search. I tried several times in different VB machines to make the package but result same. I can however start the application program from win explorer by click .exe file without any trouble. Also if I go through "browse" button on that "Missing shortcut" box to find my .exe file and execute it, I then can start the application from Start|Program straightly without that "Missing shortcut" box anymore. This should not be the normal if the application correctly installed. Is something wrong with my VB program or the procedures in doing Package & Deployment method?

    I havent touched much abt VB.NET which seems changed a lot from VB6. Does anyone know how VB.NET handle this exe file issue (running on non-VB machine)?

    David

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •