[RESOLVED] VB6 and Windows 7

[RocketRon]

Hi
Trying to run Vb from within win 7 as administrator with administrator rights
firstly I get an error DAO350.dll missing.
Internet searches say it is the DAO350.dll corrupt copy a fresh copy from
CD and register. tried that and get an error 0x80004005 is there any solution
to getting VB6 to run from Win 7 in compatibility mode?
Hi Moderators
If you are not happy with this item in VB6 can you give me a link where
I can see if it will work or not. At the moment very frustrated.

[Doogle]

If you look here: http://msdn.microsoft.com/en-us/vstudio/ms788708 you'll see that DAO 3.5 is not supported under Windows 7. I guess you'll have to use DAO 3.6. However, DAO is really old technology and you should be using ADO

[RocketRon]

Hi Doogle
Thanks fo your reply I understand about DAO and I have not used it since very
early on when I started reading programs from text books.
Why does Win 7 think its missing when I dont want it anyway.
Is there a work around?

[Doogle]

Well, the error you're seeing implies that you're using DAO. I believe you can get DAO 3.6 which will work.

[RocketRon]

Hi Doogle
Yes I have DAO 3.6 on PC and CD.
AS DAO is part of Microsoft Jet how the
hell do I find the program its in?
Access or VB
I know one program I have on my PC has Microsoft.Jet 4.0
but I do not see any ref to DAO. Knowledge somewhat limited.

[RocketRon]

Hi
I had a thought if I remove DAO350 from the references do you
think that would resolve the issue.
If yes what is the correct path?

[Doogle]

I guess you'll have to remove the Reference to DAO 3.5 and replace it with a reference to DAO 3.6. The Path to DAO 3.6 is wherever you put it. I'd guess C:\Windows\System32\ but as I don't have access to W7 I can't be sure.

[dilettante]

DAO isn't "part of Jet" and no version of it has been part of MDAC/DAC for a long, long time so anything more recent than Windows XP that was installed originally as SP1 or RTM probably will not have it unless you put it there.

Modern versions of Access have their own "private" version of DAO. If you program against that you'll have to redistribute the correct version matching the version of Office/Access you targeted.

For Access 2007 that's called "Microsoft Office 12 access database engine object library" when you hunt for references to add.

If you want to limp along using DAO in VB6 with Jet MDBs in earlier formats (Access 2003 & 2000 both use Jet 4.0 as far as I know) you'll have to deploy the "crutch" DAO 3.6 yourself. This was a stopgap to give people time to port to ADO and was not meant to live this long.

The DAO 3.6 library normally gets installed on development machines when you install VB6 SP3 or later, in case you are still trying to keep old VB5 DAO programs alive. But it isn't "part of" either VB6 or Access, it is a separate library like so many others. It also requires deployment though there isn't a really clean way to do it. A manual process is described in How To Redistribute DAO 3.6.

[RocketRon]

Hi PowerPoster
Thank you for the information I understand now about DAO but
what I cannot understand and you may be able to answer the
question.
I wanted to load VB6 SP6 on the same partition as Win 7 there
are no VB programs on that partition and I am not trying
to open one, why do I get an error to say DAO350.Dll is
missing?
I do have VB on another partition running XP Pro SP3.

[firoz.raj]

just copy dao350.dll from the internet . and copy inside system32 folder .when this done .try to register using regsvr32 .rather than using dao350.dll i will suggest to use dao360.dll as doggle suggested .

[RocketRon]

Hi firoz.raj

Thanks for your post I had tried to register DAO350.DLL before but it failed this
time I found what I was doing wrong and I received the message that it had
registered successfully.
Got quite excited and then ran VB only to get the same message as before
DAO350.DLL missing any thoughts?

[Doogle]

@Ron - Wouldn't it be less time consuming to bite the bullet and convert to ADO ? I don't think it's a mamoth task and you would be, to some extent, 'future-proofing' the Application.

[RocketRon]

Hi Doogle
This is what I do not understand fully I have not used DAO for years
I always use ADO so when I select VB6.Exe to open a new project
why do I get this error?
Is there something I should delete there?

[Doogle]

Ah, I think I understand - you're getting the problem when you start the IDE under Windows 7 (?) as opposed to running a VB Application which uses DAO (?)

Have you read this: http://www.fortypoundhead.com/showco...sp?artid=20502 ? There's quite a lot of useful information
eg

Some things I ran into that I didn't see mentioned is that when registering OCX and DLL files the file MUST be placed in the C:WindowsSysWOW64 directory. I know, I know... it seems the reverse of what you should do. You MUST also use the regsvr32.exe file in the SysWOW64 folder (not the one in the System32 folder) to register the files. One other tip is to ALWAYS install everythig as "administrator". I found that I also had to modify the properties of the VB6.EXE file (in the compatibility tab) to "run as administrator".

[RocketRon]

Hi Doogle and all the other posties on this thread

Worked like a dream Thank you all very much.

Hopefully one last question on this thread do
I have to now run the SP CD's not sure if I have
them all but I do have SP5 and SP6?

[Doogle]

I'd apply SP6

[RocketRon]

Hi Doogle

Thanks I will do that.
Thanks again for your help.