Re: Distributing MDAC with VB Application
From: Ken (kefford_at_tricom-tech.com)
Date: 08/13/04
- Next message: Sivaprasad: "Re: Explorer.exe issue"
- Previous message: Andreas Maurer: "Help with RegisterDeviceNotification needed"
- In reply to: MikeD: "Re: Distributing MDAC with VB Application"
- Next in thread: MikeD: "Re: Distributing MDAC with VB Application"
- Reply: MikeD: "Re: Distributing MDAC with VB Application"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Aug 2004 13:58:50 GMT
Thanks very much for your help.
It turns out that yes I am using the fm20.dll in this application, but I did
not know there was such a limitation or restriction. The provided link
clarifies a great deal for me. I think this is exactly the problem. I will
remove it.
In answer to your other questions,
- yes, I am using both DAO3.6 and ADO in this application. Is this a
problem?
- The version of MDAC_TYP.EXE is 2.8.
Is there something else I need to include if using MDAC 2.5 or higher? I
assumed that PDW would look after the dependencies. I also noticed that the
msjet40.dll is included in the CAB.
Thanks again, this helps a lot.
Sincerely
Ken
"MikeD" <nobody@nowhere.edu> wrote in message
news:%23wD8rhMgEHA.1344@TK2MSFTNGP11.phx.gbl...
>
> "Ken" <kefford@tricom-tech.com> wrote in message
> news:NTKSc.18956$x7h.5939@news04.bloor.is.net.cable.rogers.com...
> > I have built an application in VB6 that incorporates an Access2000
> > database for data storage. I am using the Package and Deployment Wizard
> > to build an installation program for the application. However, during
> some
> > attempted installations the application when run generates the following
> > error message "Runtime error 7 out of memory".
> >
> >
> > I have a working theory that the problem is maybe due to MDAC not being
> > installed properly during setup. Does this seem logical?
>
> Not to me.
>
> > If so, how does
> > one install MDAC with a Package and Deployment installation? The
> > wizard does include the MDAC installation EXE in the setup CAB but it
> > does not appear to install it.
>
> It's a silent install when run by Setup1 (the main setup program used by
> PDW).
>
> > Must this EXE be run manually?
>
> No, not usually.
>
> > Or, is there
> > another cleaner way to automatically install MDAC during setup?
> >
>
> Not really. Setup1 just runs mdac_typ.exe, but with a command line switch
to
> run it silently.
>
> I don't think MDAC has anything to do with this. At least, that wouldn't
be
> my first guess. You need to determine the line of code in your
application
> that's causing this error.
>
> You're not using MSForms 2.0 (FM20.DLL) are you? This error is quite
common
> if using that DLL in VB. That DLL is not intended for use in VB and you
> shouldn't use it under any circumstances. See the following:
>
> PRB: "Error 7 - Out of Memory" Error Message From Visual Basic Application
> Using FM20.DLL
> http://support.microsoft.com/default.aspx?scid=kb;en-us;241245&Product=vbb
>
>
> > The error seems to be only when the application is installed on a
> > computer that does not already have Access2000 installed. I have
> attempted
> > to isolate any DLL or OCX files that may be missing under these
conditions
> > by comparing the SYSTEM directories of a known good install to a bad
> > install. The only files that seem not to be present after installation
> > when the problem occurs are the following,
> > dao360.dll
> > msado15.dll
> > msderun.dll
>
> In reference to the above. What version of mdac_typ.exe are you including
> in your package? Versions of MDAC *after* 2.5 do NOT include the Jet
> components. Also, are you using both DAO 3.6 and ADO in your app?
>
> Mike
>
>
- Next message: Sivaprasad: "Re: Explorer.exe issue"
- Previous message: Andreas Maurer: "Help with RegisterDeviceNotification needed"
- In reply to: MikeD: "Re: Distributing MDAC with VB Application"
- Next in thread: MikeD: "Re: Distributing MDAC with VB Application"
- Reply: MikeD: "Re: Distributing MDAC with VB Application"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|