Re: Access 2007 and VB
- From: Tom Shelton <tom_shelton@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Oct 2008 15:47:41 -0500
On 2008-10-20, Ralph <nt_consulting64@xxxxxxxxx> wrote:
"LondonLad" <LondonLad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C503FAFC-DAEA-46CB-9C8B-860A06C6DB57@xxxxxxxxxxxxxxxx
Hior
I have a Access 2003 DB with the extn mdb which works fine with
my VB6.
strConnection = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" _
& App.Path & "\AccessFile\BookData.mdb"
I now have Access 2007 when I load the file BookData.mdb Access recomends
to convert to the new file enhancement which gives the extn accdb
strConnection = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" _
& App.Path & "\AccessFile\BookData.accdb"
When I convert as above I get the error:
"unrecognized database format"
Does that mean that I cannot run any Access files I create in the future
is there
some other way to do this?
Ron
There is a bit of confusion with ADO access to the new MSAccess ACCDB
format. The reason is that OLEDB and ODBC support was released after the new
format was released, and then it sort of just dribbled out. <g> I'm going to
bore you with the tedious details because it will help when your run across
various articles and post that may appear contradictory. The authors were
likely correct at the time, but things changed.
1) ACCDB was released. But not ADO/ODBC providers or drivers, thus ADO/DAO
was not supported.
Developers were encouraged to use the dotNet access libraries.
2) ADO/ODBC providers were released but tied to an MSAccess license. ie, you
and the target had to have MSAccess to "legally" distribute the provider.
You got the provider thru MSAccess updates.
3) You can now download these providers separately. I have no idea if the
license requirement still stands or not. Since MSAccess says you can't
without a license, but the download appears to contain no restriction????
http://www.microsoft.com/downloads/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en
So, Yes, Virginia there is ADO access to the new format. However, features
will vary.
Meanwhile, MSAccess team also introduced a new ACEDAO. Which is essentially
a new DAO built on ACE (which is nothing more than a new Jet). This brought
about some confusion because many tools would do a bit of magic behind the
scenes. You could reference "DAO". And if the file format was Jet 4 - You
got DAO 3.6, but if it was accdb, you got ACEDAO - without any warning or
notification back to the developer.
Meanwhile, MS stopped support of the MDAC component suite with Vista,
introducing instead the DAC 6.0. Which lead to speculation that there was a
NEW ADO. But there wasn't. The initial DAC was functionally equivalent to
ADO 2.8. Meanwhile, MS then started shipping a "Microsoft ActiveX Data
Objects 6.0 Library". While there are subtle differences, this library (at
this time) is supplied from a developers point of view to mainly just
provide symmetry - eg "Microsoft ActiveX Data Objects 2.8 Library" matches
MDAC 2.8, and "Microsoft ActiveX Data Objects 6.0 Library" to match DAC 6.0.
[I'm thankfully not even going into automation, dotNet aspects, interop, or
the new VSTO.]
Confused yet? I am. <g>
The ADO/ODBC drivers are no longer handled by the SQL Team. The MS Office
Team has taken over their development and release. So I would expect the
same pattern to continue. Features only availble thru Office, then
ADO.Net/VSTO, then perhaps grudingly support for the past. <g>
Purely a personal opinion, but I would take MS's and those of its minion's
(mvps, vendors, etc.) major pronouncements on the viability or obsolesces of
these technologies with a grain of salt. MS has a long history of 'wishing'
things to be true that don't quite happen. For example, with the
introduction of ADO MS pronounced DAO dead. No more advancements, if you
used DAO you were stupid and behind the times, etc. But it hung around. And
then rather silently DAO 3.5 and 3.6 showed up. Doesn't have all the
features of ADO - but on a desktop DAO did and still out performs ADO and
remains viable for Jet 4.
For awhile, MS pronounced Jet dead. "Use MSDE instead with MSAccess
projects", blah, blah, - Now MSDE has slid into retirement and Jet/Access
are doing just fine thank you.
I see the same thing happening with accdb - what did the Office crew come up
with for managing the new format? ACEDAO!
Hope I wasn't too boring and this helps you decipher the information that is
out there. You have to examine the date of the article/blog/post and then
also the author's agenda. <g>
-ralph
Ralph,
MSDE was replaced with SqlServer Express 2005.
--
Tom Shelton
.
- Follow-Ups:
- Re: Access 2007 and VB
- From: Jeff Johnson
- Re: Access 2007 and VB
- References:
- Access 2007 and VB
- From: LondonLad
- Re: Access 2007 and VB
- From: Ralph
- Access 2007 and VB
- Prev by Date: Re: Access 2007 and VB
- Next by Date: internet file transfer control in vb6
- Previous by thread: Re: Access 2007 and VB
- Next by thread: Re: Access 2007 and VB
- Index(es):
Relevant Pages
|
