I am really getting frustrated on this!

Ok we have a couple of apps in VB5 which worked fine with Access97. Some mental giant decided it would be a really good idea to upgrade everything to Access2000. Die lamer Die.

Ok DAO connections don't work, so posted a question about this on a couple of boards, and was informed that we needed to use DAO3.6, (which apparent gets loaded with Access2000.

This is the problem:

IN vb's components and references there is no mention of DAO3.6, we still only have the 97 versions. Anyway found out how to get around this? The local Microsoft help line are their usual total waste of space on the issue.

surely in the vast legions of MS product users l am not the only one to have this problem:(

Where do l get DAO3.6

Jethro

I had a look at the references in Access 2000

I have DAO 3.6 and have attached it.

I haven't installed it specifically so it must install with an application.

I am using W2K Prof
Standered VB5 Enterprise Install
Stadered Office 2000 Prof Install

I have attached the DLL but don't know if this refereces something else

Hope this is of use

Doh!

It won't let me attach it

Jethro

I've got it, I've got VS6 enterprise SP5, Access 2000 and MDAC 2.5 SP1 here at home, I could be wrong but my memory says MDAC installed it.

I'm pretty sure that this is like Microsoft Query - it comes with the package but doesn't intall by default. Check you original Access 2000 - it should have DAO 3.6 - alternatively, why not re-write for ADO. You'll have to evntually and it really isn't that hard...

Cheers,

P.

Found This In MSDN

DAO Overview
Access 2000 includes the 3.6 version of the DAO library, a maintenance upgrade to the 3.5 version that shipped with Access 97. (The basic architecture and functionality is very similar between versions.) DAO relies on a workspace object model for types of data access. The workspace object can contain session, security, and transaction information. (A workspace object defines how your application interacts with data.)

....am guessing will need to go through the Project->References->Browse thingy to find the naughty DAO3.6 somewhere in the Office directories....hmmm...maybe vb only checks the windows directories.

PaulW

ADO is the biggest piece of ****e l have ever had the misfortune to run across. Currently am using it...and hating it....does not contain the flexibility of DAO for database access and searching.

This is a microsoft thing. Other languages allow easy connection to various db formats without having to find strange objects hidden away under the bonnet of the OS, see OI, Delphi etc to see what MS could have made VB database connections.

Ok thats my $.02c rave for the day out of the way.

All

Thanks for the help guys.........