I have a pretty simple app I'm trying to distibute
using a SETUP and .CAB.

The app has one form, no modules, and the
following references added to the basic ones:
   - OLE Automation
   - Microsoft DAO 3.6 Object Library

The only components added are:
    - Microsoft Data Bound Grid Control 5.0 (SP3)
    - Microsoft FlexGrid Control 6.0 (SP6)

I'm running XP and installed the package on a
pretty-much virgin machine running XP. I got
no error messages during the install.

When I run the app, I get the "really helpful" error message:
CLASS NOT REGISTERED
Looking for object with
CLSID 0000010-0000-0010-8000-00AA006D2EA4

I have no clue what to do with that information.

I ran the gridfix.exe  that is supposed to fix the
problem with dbGrid not getting registered, and
it seemed to run okay, but I still get the error.

I suspect that the gridfix.exe doesn't work with XP.
I have previously used this fix on other machines
when distributing dbgrid and it worked.

In the same package, I included another EXE
which uses no grids nor DAO and that program
worked fine, despite having a lot more components
and other junk in it, so it would seem that the
problem *has* to be with the grids or DAO.

Am I missing something?

Nelson Ford

Every control has a unique ID, a "Class ID".
You can look it up in the Registry under the
HKCR\CLSID key. If you look up the number you
copied you'll see it's the DAO.DBEngine. On my
machine that's DAO350.dll. I'm not familiar with
that. Someone else may know more about it.
But it sounds like your target machine may not
have necessary database components installed.

Show quoteHide quote

Thanks for the info. The SETUP.LST file for the installation
shows the DAO file in it, but I can't find it in the target machine.
So I downloaded it from the web, copied it into System32,
and ran RegSvr32 on it, got a confirmation that it was registered.
Ran my app, and got the same error message.


Show quoteHide quote

You're probably missing other files too.  There's more than 1 file to DAO
(and Jet).

You used the Package and Deployment Wizard, right?  It *should* have
included all the files necessary for DAO. For reference, here's what it
should have included:

[DAO360.dll]
Dest=$(MSDAOPath)
Uses1=MSJet40.dll
Uses2=MSJtEr40.dll
Uses3=MSJInt40.dll
Uses4=MSJtEs40.dll
Uses5=VB5DB.dll
Register=$(DLLSelfRegister)
CABFileName=MSDAO360.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABRunFile=MSDAO360.exe -Q

[MSJet40.dll]
Register=$(DLLSelfRegister)
Dest=$(WinSysPathSysFile)
Uses1=MSJtEr40.dll
Uses2=MSJInt40.dll
Uses3=VBAJet32.dll
Uses4=MSWStr10.dll
Uses5=MSWDat10.dll
Uses6=MSRD2x40.dll
Uses7=MSRD3x40.dll
Uses8=MsRepl40.dll
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MSJtEr40.dll]
Dest=$(WinSysPathSysFile)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MSJInt40.dll <0009>]
Dest=$(WinSysPathSysFile)
CABFileName=J4ResENU.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=J4ResENU.inf

[MSJtEs40.DLL]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MSWDat10.DLL]
Dest=$(WinSysPathSysFile)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MSWStr10.DLL]
Dest=$(WinSysPathSysFile)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MSRD2x40.dll]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MSRD3x40.dll]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

[MsRepl40.dll]
Dest=$(WinSysPathSysFile)
CABFileName=MSJet40.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSJet40.inf

(the above copied and pasted from VB6DEP.INI)

Quite honestly, I don't even know if the above list of files is complete.
But the Super Bowl is starting now so I have to go. <g>

Show quote Hide quote Yeah, I used the PDW, but for some reason, it
didn't include all that stuff. I was using the 3.6
data control, which I didn't need because I am
using an Access97 database, so I changed it to
3.51, then when I ran the PDW, it added a lot
of stuff (but nothing like your list below).

Then when I tried the install-and-run again, I
didn't get the same error message, but I got one
saying "Err. 3447: Jet VBA failed to initialize
when called. Try installing the program again."

I've got an installation package from 2004 for
an app that uses similar files as this app, so I
installed it and then the new program works ok,
but then the *old* program won't run!

Below is a list of files from SETUP.LST for the
old program. I tried putting these same files in
the new package, but it still won't work.

File1=@MDAC_TYP.EXE,$(AppPath),,,1/20/00 12:00:00 AM,7856352,25.0.4403.12
Fil***@MSCOMCTL.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 12:00:00 AM,1066176,6.0.88.62
Fil***@DBLIST32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,200496,6.0.81.69
Fil***@MSDERUN.DLL,$(CommonFiles)\designer,$(DLLSelfRegister),$(Shared),7/15/00 12:00:00
AM,136192,6.0.88.4
Fil***@msstdfmt.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),7/15/00 2:13:16 PM,118784,6.0.88.4
Fil***@MSHFLXGD.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 12:00:00 AM,438976,6.0.88.4
Fil***@dbgrid32.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 10:55:26 AM,525352,5.1.81.4
Fil***@MSADO25.TLB,$(WinSysPath),$(DLLSelfRegister),$(Shared),8/29/02 5:00:00 AM,81920,2.71.9030.0
Fil***@msflxgrd.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 3:58:12 PM,244416,6.0.84.18
File***@VB5DB.DLL,$(WinSysPath),,$(Shared),6/18/98 12:00:00 AM,89360,6.0.81.69
File***@msrepl35.dll,$(WinSysPathSysFile),,,4/26/00 1:34:56 PM,415504,3.51.3225.0
File***@msrd2x35.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,4/26/00 1:34:50 PM,262144,3.51.623.0
File***@expsrv.dll,$(WinSysPathSysFile),,,5/11/03 10:35:32 PM,380957,6.0.72.9589
File***@vbajet32.dll,$(WinSysPathSysFile),,,5/11/03 10:35:32 PM,30749,6.0.1.9431
File***@msjint35.dll,$(WinSysPathSysFile),,,4/26/00 1:35:02 PM,139264,3.51.623.0
File***@msjter35.dll,$(WinSysPathSysFile),,,4/26/00 1:34:56 PM,24848,3.51.623.0
File***@msjet35.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,4/26/00 1:34:48 PM,1050896,3.51.3328.0
File***@Dao350.dll,$(MSDAOPath),$(DLLSelfRegister),$(Shared),6/10/99 9:34:04 AM,570128,3.51.1608.0
File***@Dao2535.tlb,$(MSDAOPath),$(TLBRegister),$(Shared),8/29/99 5:50:26 AM,73184,0.0.0.0

Show quote Hide quote I Googled the "Jet VBA..." error message and found this:
http://www.hayessoft.com/support/download/system_utilities.htm
which fixed the problem.

Microsoft has more money than God and an infinite
number of beta testers to draw on, yet they can't
seem to produce software that works right, or even
to provide their own fixes.

    Even more amazing, the beta testers number in the
hundreds of thousands and all are sucker enough
to work for free!

    I expect that getting fixes from MS is only going
to get worse. I recently needed an MDAC update
and MS wouldn't let me have it because they wanted
to first run their snoopware to confirm that I had the
"genuine advantage" of having paid for Windows. At the
same time, their snoopware won't run on my Win98
system. So it's a catch-22.
    MS is bluntly refusing updates to Windows
users who aren't on XP, while making it appear that
they're only taking reasonable steps to protect
themselves from "pirates".

Show quote Hide quote Well, in the early days of VB, I did some beta testing
for them. The motivation was in trying to get the
program to work right and to have features that we
wanted. Plus, we got a free copy of the finished
program, so it wasn't completely for free.

But I don't think MS put in place the resources
to handle all the feedback they got. It wasn't unusal
to get the finished program and find bugs in it that you
had reported to them.




Show quoteHide quote

Well, it seems *not* to have fixed the problem.

So I have deleted all the deployment package
and started over, but I get the same "Jet VBA
will not initialize" message.

I'm into my second day now of simply trying
to bundle up an application to distribute.
I thought the hard part was over when I finished
the app.

Code to sort out different dates
How to write to Excel spreadsheet programmatically?
Using timers
String comparisons in VB6
Sound??
Irritating WebBrowser?
Text box Validation
Getting a specific instrument's sound from an mp3 file?
Listview
Class as an array