DAO to ADO

whomademe

New member
Local time
Today, 04:53
Joined
Jan 4, 2018
Messages
4
I am starting to look at converting my DAO to ADO in our access system.

I am thinking this, as I want to create myself a roadmap to ultimately converting to TwinBasic (sitting over MSAccess, and later on, SQL server)

Do I need to? Can I port across and use DAO, or should I move?

If so, is there any resource on pitfalls, workarounds, etc?

Thanks....
 
I would not do such a conversion. Trading time for value, I would get going in TwinBasic--which supports DAO anyway--long before I would convert an exiting DAO application to ADO.
 
Be aware that reports do not work with ado recordsets and some form functionality such as filter and sort will generate an error (although you can write your own )

You have to set the option to use ANSI 92 for forms/reports to work with ADO - but ANSI 92 is over 30 years old and in terms for filtering, quite restrictive on what can be used - and I would expect DAO to no longer work
 
If you are using Access as your data there in point whatsoever in converting. ADO is slower and less flexible.
 
Be aware that reports do not work with ado recordsets and some form functionality such as filter and sort will generate an error (although you can write your own )

You have to set the option to use ANSI 92 for forms/reports to work with ADO - but ANSI 92 is over 30 years old and in terms for filtering, quite restrictive on what can be used - and I would expect DAO to no longer work
Are you sure about all of that? It is true that disconnected ADO recordsets do not work with reports but don’t remember there being a general issue. Similarly with ANSI 92
 
Are you sure about all of that?
It’s been a while (although I use disconnected recordsets for a number of things) so perhaps things have changed but that is my experience
 

Users who are viewing this thread

Back
Top Bottom