Can't get DAO app to run on a 2000 machine 1

[krudler]

Ok, clearly I am not the brightest crayon in the box when it comes to some of this....but here is my problem:

We have this application (read:inherited from someone else) that was written in VB5 running on an old Windows NT server using DAO to Access an Acc98 mdb. As part of our migration of everything over to a new 2000 server the task at hand was to get this job over there as well - naturally, it does not work. I keep getting a vague dialog box that just says "Data Access Error". Clearing this then produces the ubiquitous "Run Time Error 91".

I've converted the mdb to Access 2000, figuring that was the most obvious issue, but still get the same. Reviewing the dependencies for the original VB5 app I see it was using DAO 3.5, so I recompiled it with VB6 and now it is DAO 3.6 - but still get the same.

Now I figure either
1> since the app was originally using Jet 3.5 or 3.6, maybe it doesnt work now since the 2K server is Jet 4.0?
2> I may have to go and recode the whole thing to be ADO...this sounds great (and would be better, in my opinion), but this is a pretty big mess of code and I am loathe to have to go re-write the whole thing.

The dao360.dll that the app is using (now, was dao350.dll before) is installed on the 2K server....I really don't know where else to go....can someone help at least point me in the right direction?

Thank you soooooooooooooooo much......

 

[dyarwood]

I'm assuming you have selected to use the DAO reference in the modules from the tools menu.

 

[krudler]

Yeah, its the "Microsoft DAO 3.6 Object Library".
thanks...

 

[krudler]

I guess I don't also need to reference some kind of Jet object library? It doesn't seem to need to it...the program compiles fine....am I correct to assume that the DefaultType propery of "2-Use Jet" on the Data Control will just use whatever the appropriate Jet driver on the machine or the db in question is?

 

[SonOfEmidec1100]

Try installing MDAC 2.7 or 2.8 this fixed some issues I had with DAO36 (after installing W2000sp4 I think)

 

[krudler]

Thanks SonOfEmidec,

But MDAC 2.7/2.8 are not solving my problem. Reinstallation of Jet4.0 is not either. Through further debugging on my local machine I can now at least get a more intelligible error that says "Unrecognizable database format (filename.mdb)". I'm not sure why that would happen? The database itself used to be Access97, but I have converted it to both 2000 and 2002 and it's not happy with those either.
Am I right to figure that there is some inherent incompatibility with the 'good old' Data Control that this project is using (as opposed to the MS ADO Data Contol 6.0) with DAO and the more current versions of Access - 2000 and 2002? Or is there just something else my clouded mind is missing?
Thanks for any help....I'm getting close to pulling hair....

 

[azrobert]

Have you installed vb service pac 5 ?

that fixed that error for me

http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/dnldoverview.aspx

 

[krudler]

AZROBERRRRRT!!!!
Bless you!!!

Being a bonehead, I had forgot to check that - see, when they gave us all new desktop machines a few months back they "reinstalled" all our software. I never thought to double check and make sure they had installed SP5, I guess I took it for granted.

Still, you would think I would have thought something was up when "Access2000" was not appearing as a valid option under the DataControl.Connect property list. After applying SP5 and selecting Access2000 for the DataControl.Connect propery and re-compiling, it seems to work!!
AND I STILL HAVE HAIR LEFT!!

Thanks sooooooooooo much! This site rules

 

[azrobert]

I do the bonehead thing at least once a day

You are right,

I could not live with out This site !
(I go through withdrawls when it is down)