DAO vs ADO (or, "Why Is This App Blowing Up?")

[krudler]

I have this app that I need to migrate over to another server. The gal who originally put this together used DAO 3.5 and it was running on an NT server. When I move this thing over to a 2000 server, I was getting an error. I was astute enough to realize that the msdao350.dll was missing, so I added it and registered it. That cleared up the original error but now I get a generic "Data Access Error", then it spits out a run time error 91, presumably b/c the control was unable to be bound to anything. The app is trying to get to an Access db using Jet (assumably 3.whatever, it was not written for Jet 4.0...but the mdb is Access98 anyhoo).
Do I have to go in an recode this whole thing to use ADO or something, and add the ADO controls to the project and so on, or is there something else I am missing that would make the 2000 server more backward compatible to this app?
HELP!!!

 

[psemianonymous]

I'm speaking from a strictly Access-standpoint.

1. 640kDAO 3.5 is good enough for anybody. OK, well, you shouldn't have to upgrade anything, so long as your database MDB itself has not upgraded to 4.0.
2. If you have just upgraded to a Win2k-based file server, make sure it is running service pack 3. Maybe it has nothing to do with your problem...then again, maybe it does.
3. I don't know how early/late binding works in VB, so I'll just give you the ambiguous "it can't hurt to declare your recordsets as DAO.Recordset so that any ambiguities are removed". Again, disclaimer: I don't know.
4. minor correction: Access98 -> Access97

So I recommend you try #2. That is all.

 

[SonOfEmidec1100]

I agree with foolio -

It should work without any changes. A common problem is that Windows 2000 pre SP3 did not install the required MDAC components. I would confirm/install SP3 before checking anything else.

If it still does not work maybe try Jet40sp6_w2k

 

[SonOfEmidec1100]

Er DAO3.5
Probably should have said Jet35sp3.exe

Im putting my money on the SP3 anyway.

 

[krudler]

SP3 is installed, but perhaps the MDAC components are not up to snuff for some reason, I'll check on that.
Thanks!

 

[SonOfEmidec1100]

I now suspect that the VB program has a reference to the DAO350.DLL which is no longer generally installed. You need to install Office 97 or Vb6 or goto this very useful site

http://support.microsoft.com/default.aspx?scid=/servicedesks/fileversion/dllinfo.asp&SD=MSDN&FR=0

Then type in DAO350.DLL then click more info it will tell you available sources of the dll

Good luck

 

[SonOfEmidec1100]

What I meant to add was maybe instead you could change the program reference to a later DAO object library (3.6?) but I dont know if there will be any undesired side effects.

Any views out there ?

 

[hello07]

Dear Sir,
Can you please tell me how to access Oracle 8i using Data Access Object (DAO) through Visual Basic. i have used DAO in accessing Microsoft Access but dont know how to access Oracle by the same method. i would be greatfull if you please give me a solution.
Thank You,
himadrimukherjee07in@yahoo.co.in

 

[krudler]

I've tried both registering DAO350.dll as well as changing the reference in the project to DAO 3.6. I still get the same vague error.....d'oh

 

[psemianonymous]

Your problem may be as generic as a path change. Ensure that your table links to the backend are working, or however you do it, make sure the path/filename is correct.

 

[SonOfEmidec1100]

Maybe this MSDN item will give you some clues such as do all the jet core files exist

Q240377 HOWTO: Insuring Jet 3.5 Is Installed Correctly