Michael
Jul 25th, 1999, 03:29 PM
I have just installed Service Pack 3 and I would appreciate a little advice regarding ADO/DAO/Jet.
I have just spent half of the morning on the Microsoft web site trying to find out answers to my questions and I just cannot find what I need. Perhaps some of you good people can help me.
It is our corporate policy to keep (reasonably!) up to date with the latest development version of Dev Studio.
Microsoft are telling us that new developments should be written using ADO. We are perfectly happy for the present with DAO since we know that Microsoft will not drop it overnight (although we assume that they will drop it eventually). Therefore please do not advise us to switch immediately to ADO!!!
It is my understanding that the DAO 3.6 in SP3 uses the Jet 4 engine, which is what is being used in Office 2000.
We are using Office 97 and therefore currently use DAO/Jet 3.51.
The first piece of advice I need is this. Should I update all of my current projects to use DAO 3.6 or will it be a waste of time if we are sticking to Access 97 for the time being? Will we get any extra functionality? Or should I wait until we upgrade our Office version to 2000?
The second piece of advice I need relates to ADO. I have heard that there are serious performance issues regarding ADO with Access databases and that DAO is far superior speedwise. Can anyone (a) confirm or deny this, and (b) if it is true, quote me any statistics on this?
Finally (phew!) does anyone have any info (inside or otherwise!) on how long Microsoft is likely to continue supporting DAO before we are all forced to switch to ADO? I know that there are a hell of a lot of sites using Access databases, with VB front ends using DAO so Microsoft cannot just ignore this --- can they?
Well that seems like a lot of typing for 3 questions but these are all issues that I would be grateful your comments on.
Thanks in advance.
I have just spent half of the morning on the Microsoft web site trying to find out answers to my questions and I just cannot find what I need. Perhaps some of you good people can help me.
It is our corporate policy to keep (reasonably!) up to date with the latest development version of Dev Studio.
Microsoft are telling us that new developments should be written using ADO. We are perfectly happy for the present with DAO since we know that Microsoft will not drop it overnight (although we assume that they will drop it eventually). Therefore please do not advise us to switch immediately to ADO!!!
It is my understanding that the DAO 3.6 in SP3 uses the Jet 4 engine, which is what is being used in Office 2000.
We are using Office 97 and therefore currently use DAO/Jet 3.51.
The first piece of advice I need is this. Should I update all of my current projects to use DAO 3.6 or will it be a waste of time if we are sticking to Access 97 for the time being? Will we get any extra functionality? Or should I wait until we upgrade our Office version to 2000?
The second piece of advice I need relates to ADO. I have heard that there are serious performance issues regarding ADO with Access databases and that DAO is far superior speedwise. Can anyone (a) confirm or deny this, and (b) if it is true, quote me any statistics on this?
Finally (phew!) does anyone have any info (inside or otherwise!) on how long Microsoft is likely to continue supporting DAO before we are all forced to switch to ADO? I know that there are a hell of a lot of sites using Access databases, with VB front ends using DAO so Microsoft cannot just ignore this --- can they?
Well that seems like a lot of typing for 3 questions but these are all issues that I would be grateful your comments on.
Thanks in advance.