VB6: Packaging Problem

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Trevor Fairchild
    #1

    VB6: Packaging Problem

    I have an application that I've programmed - it works fine in VB6, and
    when compiled and packaged, installs and operates fine on my machine.

    When I install it on another machine (without VB6), it craps out,
    providing nothing more insightful than the WinXP message that for some
    reason the program has stopped working - would you like to tell
    Microsoft about it?

    I have put in msgboxes throughout the program to identify exactly what
    line of code it is crapping out on:

    The app opens MS Access (not visible) and copies tables, etc. within
    it. The installed version will open an instance of MS Access fine
    (and I can see it in my Windows Task Manager). The program dies out
    at the next line, however:

    myAccess.OpenCu rrentDatabase '...name of database...'

    I haven't any idea why this would be - I have read the Microsoft stuff
    on what files shouldn't be placed in the packager (msacc.olb,
    msado25.tlb) and this has made no difference. Does anyone have any
    ideas?

    Any help would be appreciated!

    Trevor Fairchild
    Tags: None
    • gonzo
      #2
      Re: Packaging Problem

      Trevor,

      Are you using the "Package and Deployment Wizard", VB Installer or a Third
      Party program to create the install package?

      Gonzo

      "Trevor Fairchild" <trevorf@e-crime.on.ca> wrote in message
      news:5bf84afd.0 308211107.7ed2d fd7@posting.goo gle.com...[color=blue]
      > I have an application that I've programmed - it works fine in VB6, and
      > when compiled and packaged, installs and operates fine on my machine.
      >
      > When I install it on another machine (without VB6), it craps out,
      > providing nothing more insightful than the WinXP message that for some
      > reason the program has stopped working - would you like to tell
      > Microsoft about it?
      >
      > I have put in msgboxes throughout the program to identify exactly what
      > line of code it is crapping out on:
      >
      > The app opens MS Access (not visible) and copies tables, etc. within
      > it. The installed version will open an instance of MS Access fine
      > (and I can see it in my Windows Task Manager). The program dies out
      > at the next line, however:
      >
      > myAccess.OpenCu rrentDatabase '...name of database...'
      >
      > I haven't any idea why this would be - I have read the Microsoft stuff
      > on what files shouldn't be placed in the packager (msacc.olb,
      > msado25.tlb) and this has made no difference. Does anyone have any
      > ideas?
      >
      > Any help would be appreciated!
      >
      > Trevor Fairchild[/color]


        Comment

        • JP
          #3
          Re: Packaging Problem

          It may be because you have different versions of office on your
          development computer and the testing computer. Try instantiating your
          access object like implicitly...

          Dim objAccess as object

          set objAccess = CreateObject ("Access.Applic ation")

          objAccess.OpenC urrentDatabase "C:\Northwind.m db, False
          ....etc

          "gonzo" <gonzo@gonz.com > wrote in message news:<QImcnVrMm YPUhtGiXTWJkw@c omcast.com>...[color=blue]
          > Trevor,
          >
          > Are you using the "Package and Deployment Wizard", VB Installer or a Third
          > Party program to create the install package?
          >
          > Gonzo
          >
          > "Trevor Fairchild" <trevorf@e-crime.on.ca> wrote in message
          > news:5bf84afd.0 308211107.7ed2d fd7@posting.goo gle.com...[color=green]
          > > I have an application that I've programmed - it works fine in VB6, and
          > > when compiled and packaged, installs and operates fine on my machine.
          > >
          > > When I install it on another machine (without VB6), it craps out,
          > > providing nothing more insightful than the WinXP message that for some
          > > reason the program has stopped working - would you like to tell
          > > Microsoft about it?
          > >
          > > I have put in msgboxes throughout the program to identify exactly what
          > > line of code it is crapping out on:
          > >
          > > The app opens MS Access (not visible) and copies tables, etc. within
          > > it. The installed version will open an instance of MS Access fine
          > > (and I can see it in my Windows Task Manager). The program dies out
          > > at the next line, however:
          > >
          > > myAccess.OpenCu rrentDatabase '...name of database...'
          > >
          > > I haven't any idea why this would be - I have read the Microsoft stuff
          > > on what files shouldn't be placed in the packager (msacc.olb,
          > > msado25.tlb) and this has made no difference. Does anyone have any
          > > ideas?
          > >
          > > Any help would be appreciated!
          > >
          > > Trevor Fairchild[/color][/color]

            Comment

            Previous template Next
            Working...