|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
#1
February 22nd, 2009, 06:39 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
DAO / ADO
I have developed an application in Acces using DAO. I want to be with the
times and convert to ADO. Is There a program to change all my code to ADO ? And what are the major advantages of ADO ? Tahnk you for advise, -- EPS 
|
|
#2
February 22nd, 2009, 07:32 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
On Sun, 22 Feb 2009 10:39:01 -0800, Emergency Power
. wrote: Leave it the way it is, and focus on more important issues. ADO is not better than DAO in a pure Access (FE + BE) environment. Also curious that you were considering changing BEFORE you knew the major advantages. -Tom. Microsoft Access MVP I have developed an application in Acces using DAO. I want to be with the times and convert to ADO. Is There a program to change all my code to ADO ? And what are the major advantages of ADO ? Tahnk you for advise,
|
|
#3
February 23rd, 2009, 01:28 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
Thank you for your response. I did ask what the major advantages were so
that I could determine if I would change. I read a few books that said if you were to make a program it was best to use ADO because DAO is likely going to be phased out. " The newer ADO is currently favored be Microsoft, meaning that ADO will continue to grow and Get better while DAO remains in Maintenance mode, which generally spells doom for the technology. If a technology is in maintenance mode today, that pretty much guarantees that it won't exist at all in the not-to-distant future." Your reply is appreciated. -- EPS "Emergency Power" wrote: I have developed an application in Acces using DAO. I want to be with the times and convert to ADO. Is There a program to change all my code to ADO ? And what are the major advantages of ADO ? Tahnk you for advise, -- EPS
|
|
#4
February 23rd, 2009, 02:18 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
I suggest you look at the publication date of those books. That advice had
me converting from DAO to ADO about six years ago. Now I've had to reconvert.
|
|
#5
February 23rd, 2009, 02:40 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
I'm in the dummy section on this topic but that might make my summary useful.
I think that they started going to ADO in 2002 and then reversed themselves and went back to DAO. The developers book that everybody considers to be the best came out in 2002 and so is "backwards" on this topic.
|
|
#6
February 23rd, 2009, 09:55 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
=?Utf-8?B?RW1lcmdlbmN5IFBvd2Vy?= .
wrote in : I want to be with the times and convert to ADO. If by "with the times" you mean the year 2000, then go for it. If you mean the present day, then don't. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
|
#7
February 23rd, 2009, 09:56 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
=?Utf-8?B?Um9kIFBsYXN0b3c=?=
wrote in : I suggest you look at the publication date of those books. That advice had me converting from DAO to ADO about six years ago. Now I've had to reconvert. Many of us saw the folly in using ADO for Jet databases at the time MS was recommending and didn't convert. I'm not sure why anyone thought it was a good idea in that environment. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
|
#8
February 23rd, 2009, 09:57 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
=?Utf-8?B?RnJlZA==?= wrote in
: I think that they started going to ADO in 2002 and then reversed themselves and went back to DAO. MS started pushing ADO in Access with the release of Access 2000, which was in June 1999. By the release of Access 2002, they'd started backtracking, and by Access 2003, had completely reversed course. Access 2007 represents a complete return to the supremacy of DAO over ADO. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
|
#9
February 24th, 2009, 01:09 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
Aye, but it was the threat of withdrawn support that motivated me. Was it
more than 6 years ago? BTW I've just converted an ADO application to DAO (local Jet DB only) and my gut feel (no precision here) is that DAO runs 25% faster than ADO in this situation. Rod "David W. Fenton" wrote: =?Utf-8?B?Um9kIFBsYXN0b3c=?= wrote in : I suggest you look at the publication date of those books. That advice had me converting from DAO to ADO about six years ago. Now I've had to reconvert. Many of us saw the folly in using ADO for Jet databases at the time MS was recommending and didn't convert. I'm not sure why anyone thought it was a good idea in that environment. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
|
#10
February 24th, 2009, 07:37 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
DAO / ADO
On Mon, 23 Feb 2009 17:09:01 -0800, Rod Plastow
wrote: BTW I've just converted an ADO application to DAO (local Jet DB only) and my gut feel (no precision here) is that DAO runs 25% faster than ADO in this situation. Doesn't surprise me a bit. ADO is still useful in an environment with heterogenous data stores in the backend. In a pure JET (ACE) database, it has no benefits that I've seen. -- John W. Vinson [MVP]
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
