ADO Library

[AG]

Starting a new Access 2007 project that will utilize ADO as well as DAO.
I have many versions of Microsoft ActiveX Data Objects Library on my
machine.
Can anyone tell me what is the version that I could expect anyone running
Windows XP and Access 2007 to have installed, so I know which one to set as
a reference?

Thanks,

 

[Tom van Stiphout]

On Thu, 17 Jul 2008 17:44:51 -0400, "AG"

2.8
-Tom.
Microsoft Access MVP

 

[Allen Browne]

My suggestion would be to use:
Microsoft ActiveX Data Objects 2.1 Library
because this will give you the best compatibility with older versions of
Access.

But I don't use this library much, so others may have other experiences to
share.

 

[AG]

Thanks Allen.
Yes, I use 2.1 when developing in older versions of Access, but this project
will be completely Access 2007.

 

[AG]

Thank you!

--

AG
Email: discussATadhdataDOTcom

On Thu, 17 Jul 2008 17:44:51 -0400, "AG"

2.8
-Tom.
Microsoft Access MVP

 

[a a r o n _ k e m p f]

WRONG

2.5 was included with Windows 2000
unless you need to go further back than that; use the most recent
version for sure (2.8 or.. 6.0 with vista)

 

[a a r o n _ k e m p f]

yah no shit you don't use ADO, you're a MVP dipshit

you wouldn't know a superior library if it hit you upsize the head

 

[David W. Fenton]

Yes, I use 2.1 when developing in older versions of Access, but
this project will be completely Access 2007.

Doesn't Access install ADOX?

 

[AG]

I am sure it does, but I have so many versions of Office and Visual Studio
installed, that I have like every version on my machine.
I am trying to find out what version a machine with just XP and Office 2007
would have, so I don't target a later version and end up with an app that
errors out on the client's machine.

 

[David W. Fenton]

I am sure it does, but I have so many versions of Office and
Visual Studio installed, that I have like every version on my
machine. I am trying to find out what version a machine with just
XP and Office 2007 would have, so I don't target a later version
and end up with an app that errors out on the client's machine.

Are you writing an Access2007 app or are you use an ACCDB for your
data store? If the latter, then this is simply not an Access
question, but an ACE question. You should make that clear when
you're not actually using Access at all.

 

[AG]

The project is an Access 2007 accdb front end with a SQL Server 2005 back
end. I like to target libraries that the client will have, so I simply would
like to know what version of Microsoft ActiveX Data Objects Library would
normally exist on a Windows XP system with Access (Office) 2007 installed.

 

[David W. Fenton]

The project is an Access 2007 accdb front end with a SQL Server
2005 back end. I like to target libraries that the client will
have, so I simply would like to know what version of Microsoft
ActiveX Data Objects Library would normally exist on a Windows XP
system with Access (Office) 2007 installed.

Well, what version comes with Access 2007? That will be installed on
every PC you're installing your app on, so it seems like the safest
choice. I wouldn't use anything other than the one installed by
A2K7 if my app is an ACCDB front end (since it can be used only with
A2K7 and not any other version of Access).

 

[David W. Fenton]

The project is an Access 2007 accdb front end with a SQL Server
2005 back end. I like to target libraries that the client will
have, so I simply would like to know what version of Microsoft
ActiveX Data Objects Library would normally exist on a Windows XP
system with Access (Office) 2007 installed.

....adding to what I said in my other post:

Of course, I wouldn't use ADO at all, since it's a completely
outdated technology and discouraged by MS.

 

[AG]

David,

What, then, is the current recommended technology? Can you point me to some
articles/links?

 

[Michael Gramelspacher]

David,

What, then, is the current recommended technology? Can you point me to some
articles/links?

see article by Andy Baron: http://msdn.microsoft.com/en-us/library/bb188204.aspx

 

[AG]

Thanks Michael,

I am quite familiar with that article and keep a printout of it handy.
It even recommends replacing DAO code with ADO, so I was surprised when
David stated that ADO was 'completely
outdated technology and discouraged by MS'. Is there any basis for his
statement?

 

[Michael Gramelspacher]

Thanks Michael,

I am quite familiar with that article and keep a printout of it handy.
It even recommends replacing DAO code with ADO, so I was surprised when
David stated that ADO was 'completely
outdated technology and discouraged by MS'. Is there any basis for his
statement?

Not within my competence to say. I have very limited exposure to SQL Server and
rely almost solely upon views, I query against as if they were Access tables.

 

[David W. Fenton]

I am quite familiar with that article and keep a printout of it
handy. It even recommends replacing DAO code with ADO, so I was
surprised when David stated that ADO was 'completely
outdated technology and discouraged by MS'. Is there any basis for
his statement?

ADP + ADO makes sense, but MS deprecates ADPs in favor of MDB +
ODBC.

If you're using linked tables (i.e., ODBC), then ADO makes no sense
at all -- you should just use DAO.

ADO has not been updated for quite a long time, while DAO is in
current development (the newest update having been in A2K7, which
introduces Jet 5, AKA, ACE).

Using ADO in an MDB means doing a lot of things unbound, and I just
don't see the point.

But, nonetheless, A2K7 includes the ADO library in its installation,
so I just don't understand why you're worrying about any ADO library
version other than the one installed by A2K7.

 

[AG]

David,

Yes, mostly I will be using DAO and forms bound to tables, views or queries
derives from tables or views.
There are a few cases where ADO makes sense in code. Especially for testing
connections. If an ODBC connection fails, the user is prompted with the
built in Access dialog. If I test connections first with ADO, I can provide
my own.
I am not 'worried' about the version. Since I have so much development
software installed (which also installes ADO), I don't know which version is
installed with 2007. If someone could tell me that, I would target that
version. If no one can tell me, I can deal with it. It is not a
show-stopper.

 

[a a r o n _ k e m p f]

again-- who needs ADOX?

CREATE TABLE

ALTER TABLE

you don't speak DDL?