Dont laugh! Ive only just been given Access 2000 on my desktop!!!! (Pass the
chalk

I am used to good old VBA in Access 97, using set db = currentdb, set rs =
db.openrecordset, etc......

How easy/hard is it to convert DAO code into ADO code?

Can someone provide me with the basics please? i.e. Opening a recordset
using ADO code.

Are there any implications in using an Access97 backend and Access 2000
frontend. (until I have completed conversion/updated my colleagues version)

Many thanks in advance.

Steve.

I'm not sure that there's much point in beginning to learn 'classic' ADO at
this late stage, unless, of course, you expect to have to support and
maintain legacy applications that use it. That said though, here's the start
page for the on-line ADO documentation ...

http://msdn.microsoft.com/library/en...dooverview.asp

--
Brendan Reynolds (MVP)


"FBxiii" <(E-Mail Removed)> wrote in message
news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
> Dont laugh! Ive only just been given Access 2000 on my desktop!!!! (Pass
> the
> chalk
>
> I am used to good old VBA in Access 97, using set db = currentdb, set rs =
> db.openrecordset, etc......
>
> How easy/hard is it to convert DAO code into ADO code?
>
> Can someone provide me with the basics please? i.e. Opening a recordset
> using ADO code.
>
> Are there any implications in using an Access97 backend and Access 2000
> frontend. (until I have completed conversion/updated my colleagues
> version)
>
> Many thanks in advance.
>
> Steve.

Microsoft created a great little whitepaper to help ease the transition.
It's called "Migrating from DAO to ADO" It shows you how to do the ADO
equevalent of many DAO operations. You can find it on the MS website or I
have a copy on mine, here: http://www.rogersaccesslibrary.com/knowledge.html

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L

"FBxiii" <(E-Mail Removed)> wrote in message
news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
> Dont laugh! Ive only just been given Access 2000 on my desktop!!!! (Pass
the
> chalk
>
> I am used to good old VBA in Access 97, using set db = currentdb, set rs =
> db.openrecordset, etc......
>
> How easy/hard is it to convert DAO code into ADO code?
>
> Can someone provide me with the basics please? i.e. Opening a recordset
> using ADO code.
>
> Are there any implications in using an Access97 backend and Access 2000
> frontend. (until I have completed conversion/updated my colleagues
version)
>
> Many thanks in advance.
>
> Steve.

I guess I should ask exactly why you want to convert to ADO? In an
All-Access environment, DAO works better, and I don't see any compelling
reason to change. The only thing you need to do is add a reference to
Microsoft DAO 3.6 Object Model and you're good to go.

Mind you, ADO is not a bad thing to learn, but it's not necessary to switch
just because you've upgraded to Access 2000.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L

"FBxiii" <(E-Mail Removed)> wrote in message
news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
> Dont laugh! Ive only just been given Access 2000 on my desktop!!!! (Pass
the
> chalk
>
> I am used to good old VBA in Access 97, using set db = currentdb, set rs =
> db.openrecordset, etc......
>
> How easy/hard is it to convert DAO code into ADO code?
>
> Can someone provide me with the basics please? i.e. Opening a recordset
> using ADO code.
>
> Are there any implications in using an Access97 backend and Access 2000
> frontend. (until I have completed conversion/updated my colleagues
version)
>
> Many thanks in advance.
>
> Steve.

Unless I'm mistaken (which is, of course, always a possibility! :-) that
article appears to be no longer available from Microsoft's site, Roger. When
I searched MSDN for that title, the search returned only other articles that
refer to that article, such as the one below (note that the article below,
while still available, has been moved into the MSDN archive)

http://msdn.microsoft.com/archive/de...l/daotoado.asp

--
Brendan Reynolds (MVP)

"Roger Carlson" <NO-Rog3erc-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Microsoft created a great little whitepaper to help ease the transition.
> It's called "Migrating from DAO to ADO" It shows you how to do the ADO
> equevalent of many DAO operations. You can find it on the MS website or I
> have a copy on mine, here:
> http://www.rogersaccesslibrary.com/knowledge.html
>
> --
> --Roger Carlson
> Access Database Samples: www.rogersaccesslibrary.com
> Want answers to your Access questions in your Email?
> Free subscription:
> http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L
>
> "FBxiii" <(E-Mail Removed)> wrote in message
> news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
>> Dont laugh! Ive only just been given Access 2000 on my desktop!!!! (Pass
> the
>> chalk
>>
>> I am used to good old VBA in Access 97, using set db = currentdb, set rs
>> =
>> db.openrecordset, etc......
>>
>> How easy/hard is it to convert DAO code into ADO code?
>>
>> Can someone provide me with the basics please? i.e. Opening a recordset
>> using ADO code.
>>
>> Are there any implications in using an Access97 backend and Access 2000
>> frontend. (until I have completed conversion/updated my colleagues
> version)
>>
>> Many thanks in advance.
>>
>> Steve.
>
>

Ah, I see.

I thought ADO was the 'new' way of doing things. If DAO is OK I will stick
with it. (I have been using for 5+ years so I was a bit concerned about
'updating' my skills.

Phew! Back to worrying about the little niggles of conversion, like where
does error number -2147352567 come from and why????

Cheers,
Steve

"Roger Carlson" wrote:

> I guess I should ask exactly why you want to convert to ADO? In an
> All-Access environment, DAO works better, and I don't see any compelling
> reason to change. The only thing you need to do is add a reference to
> Microsoft DAO 3.6 Object Model and you're good to go.
>
> Mind you, ADO is not a bad thing to learn, but it's not necessary to switch
> just because you've upgraded to Access 2000.
>
> --
> --Roger Carlson
> Access Database Samples: www.rogersaccesslibrary.com
> Want answers to your Access questions in your Email?
> Free subscription:
> http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L
>
> "FBxiii" <(E-Mail Removed)> wrote in message
> news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
> > Dont laugh! Ive only just been given Access 2000 on my desktop!!!! (Pass
> the
> > chalk
> >
> > I am used to good old VBA in Access 97, using set db = currentdb, set rs =
> > db.openrecordset, etc......
> >
> > How easy/hard is it to convert DAO code into ADO code?
> >
> > Can someone provide me with the basics please? i.e. Opening a recordset
> > using ADO code.
> >
> > Are there any implications in using an Access97 backend and Access 2000
> > frontend. (until I have completed conversion/updated my colleagues
> version)
> >
> > Many thanks in advance.
> >
> > Steve.
>
>
>

It was, but that was about five years ago! :-) The 'new' way now is ADO.NET,
which has little in common with 'classic' ADO other than three letters in
its name, and is not supported in any version of Access.

Whoosh! Here comes the future of data access technology! Whoosh! There it
goes again - what was it? Whoosh! Doesn't matter now, here comes the next
one!

--
Brendan Reynolds (MVP)

"FBxiii" <(E-Mail Removed)> wrote in message
news:3A6B03AF-FC8C-478A-BD30-(E-Mail Removed)...
> Ah, I see.
>
> I thought ADO was the 'new' way of doing things. If DAO is OK I will
> stick
> with it. (I have been using for 5+ years so I was a bit concerned about
> 'updating' my skills.
>
> Phew! Back to worrying about the little niggles of conversion, like where
> does error number -2147352567 come from and why????
>
> Cheers,
> Steve
>
> "Roger Carlson" wrote:
>
>> I guess I should ask exactly why you want to convert to ADO? In an
>> All-Access environment, DAO works better, and I don't see any compelling
>> reason to change. The only thing you need to do is add a reference to
>> Microsoft DAO 3.6 Object Model and you're good to go.
>>
>> Mind you, ADO is not a bad thing to learn, but it's not necessary to
>> switch
>> just because you've upgraded to Access 2000.
>>
>> --
>> --Roger Carlson
>> Access Database Samples: www.rogersaccesslibrary.com
>> Want answers to your Access questions in your Email?
>> Free subscription:
>> http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L
>>
>> "FBxiii" <(E-Mail Removed)> wrote in message
>> news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
>> > Dont laugh! Ive only just been given Access 2000 on my desktop!!!!
>> > (Pass
>> the
>> > chalk
>> >
>> > I am used to good old VBA in Access 97, using set db = currentdb, set
>> > rs =
>> > db.openrecordset, etc......
>> >
>> > How easy/hard is it to convert DAO code into ADO code?
>> >
>> > Can someone provide me with the basics please? i.e. Opening a
>> > recordset
>> > using ADO code.
>> >
>> > Are there any implications in using an Access97 backend and Access 2000
>> > frontend. (until I have completed conversion/updated my colleagues
>> version)
>> >
>> > Many thanks in advance.
>> >
>> > Steve.
>>
>>
>>

Huh! Isn't that something! I know it used to be. That's where I got it.
Good thing I downloaded it. It's a wonderful comparison of DAO and ADO
techniques. A little dated perhaps. The author still uses:
Dim var As New Class
instead of the now-preferred:
Dim var As Class
Set var = New Class
but it does a good job of getting the average DAO user started. I still
refer to it frequently as I'm still mostly using DAO.

Thanks for pointing out that MS no longer offers it. Maybe it's because DAO
and ADO are BOTH irrelevant from Microsoft's perspective. Still, I've
noticed that Microsoft's perspective is often quite different from their
customers'.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L

"Brendan Reynolds" <anonymous at discussions dot microsoft dot com> wrote in
message news:(E-Mail Removed)...
> Unless I'm mistaken (which is, of course, always a possibility! :-) that
> article appears to be no longer available from Microsoft's site, Roger.
When
> I searched MSDN for that title, the search returned only other articles
that
> refer to that article, such as the one below (note that the article below,
> while still available, has been moved into the MSDN archive)
>
>
http://msdn.microsoft.com/archive/de...l/daotoado.asp
>
> --
> Brendan Reynolds (MVP)
>
> "Roger Carlson" <NO-Rog3erc-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Microsoft created a great little whitepaper to help ease the transition.
> > It's called "Migrating from DAO to ADO" It shows you how to do the ADO
> > equevalent of many DAO operations. You can find it on the MS website or
I
> > have a copy on mine, here:
> > http://www.rogersaccesslibrary.com/knowledge.html
> >
> > --
> > --Roger Carlson
> > Access Database Samples: www.rogersaccesslibrary.com
> > Want answers to your Access questions in your Email?
> > Free subscription:
> > http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L
> >
> > "FBxiii" <(E-Mail Removed)> wrote in message
> > news:7FA5D271-D0B4-4B94-A16E-(E-Mail Removed)...
> >> Dont laugh! Ive only just been given Access 2000 on my desktop!!!!
(Pass
> > the
> >> chalk
> >>
> >> I am used to good old VBA in Access 97, using set db = currentdb, set
rs
> >> =
> >> db.openrecordset, etc......
> >>
> >> How easy/hard is it to convert DAO code into ADO code?
> >>
> >> Can someone provide me with the basics please? i.e. Opening a
recordset
> >> using ADO code.
> >>
> >> Are there any implications in using an Access97 backend and Access 2000
> >> frontend. (until I have completed conversion/updated my colleagues
> > version)
> >>
> >> Many thanks in advance.
> >>
> >> Steve.
> >
> >
>
>

"Brendan Reynolds" <anonymous at discussions dot microsoft dot com>
wrote in news:eAd$(E-Mail Removed):

> Whoosh! Here comes the future of data access technology! Whoosh! There
> it goes again - what was it? Whoosh! Doesn't matter now, here comes
> the next one!
>

<vbg>

Tim F