Results 1 to 7 of 7

Thread: Argh. Distributed Apps:

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Jul 1999
    Posts
    78

    Post

    OK I am in a nightmare world right now.

    I just completed this monster application that needs to be installed on approximately 28 computers (it's an Access application, no problems there) but I don't want to run around and do it machine by machine.

    So, I developed a quick and dirty .exe in Visual Basic that will copy the necessary files from the network, create the directory, etc. etc.

    Only problem is that the distributed application doesn't work on anyone else's machine!

    I'm getting errors left and right when I try and run it from someone else's machine.
    I've installed the necessary MSVBVM60.DLL file, but now it's telling me that the program is missing a registered COMCNL.OCX or whatnot....
    argh!

    My question is this:

    How do I develop applications in a VB environment that will allow end-users to operate them? It's driving me nuts....

    I have the VB 6.0 Professional Edition.

  2. #2
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,175

    Post

    Is there some reason you aren't using the VB6 Packaging and Deployment Wizard?

    ------------------
    Marty

  3. #3
    Junior Member
    Join Date
    Nov 1999
    Location
    Wellsburg, WV, USA
    Posts
    25

    Post

    If you use the Package and Deployment Wizard, it will list all of the files that you need to copy and register on any target machines. These files will be located in the file Setup.lst. Use notepad to open it.

    dmuir

  4. #4
    Member
    Join Date
    Nov 1999
    Posts
    39

    Post

    i'm using the package and deployment wizard, and i'm still getting damn errors with people trying to run with program, with just about the same errors about controls not being registered.......

  5. #5
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,175

    Post

    Look in setup.lst. Is the dll being mentioned in the error messages there? If not, add it while running the P&D Wizard.

    ------------------
    Marty

  6. #6
    Member
    Join Date
    May 1999
    Posts
    49

    Post

    Necessary files for a VB set up are:

    mfc42.dll, msvcrt.dll, olepro32.dll, oleaut32.dll, stdole2.tlb, Asycfilt.dll, Ctl3d32.dll and ComCat.dll and MSVBVM50.dll

    as well as any ocx's in your project.

  7. #7

    Thread Starter
    Lively Member
    Join Date
    Jul 1999
    Posts
    78

    Post

    The main reason I haven't been using the Packaging and Deployment Wizard:
    I didn't know about it

    Thanks for the help guys, I'll look into it.

Posting Permissions

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



Click Here to Expand Forum to Full Width