R
robert d via AccessMonster.com
I've read through some posts on the ADO vs. DAO question. Most seem to be
around a year or so old.
So: I have an Access app that uses almost exclusively unbound forms and DAO
for data access. A potential client won't accept the Jet backend and demands
SQL Server.
I did some preliminary work and upsized my Jet tables to SQL server. I also
created ODBC links to the SQL Server tables from my front end. No conversion
of DAO to ADO.
Everything seemed to work pretty well. In fact, the app runs quite a bit
faster accessing data from SQL server than it does from the Jet backend on a
server.
So, since I would have to convert about 400 DAO recordsets, I'm not sure I
want to bother. Maybe the app would be faster with ADO to SQL Server, but it
is currently faster using DAO to SQL Server than DAO to Jet. So the point is,
it is not slower. Maybe that means nothing, but on the other hand, I think
it means I don't have an immediate problem. So why kill myself doing the
conversion.
Thoughts, suggestions are greatly appreciated.
around a year or so old.
So: I have an Access app that uses almost exclusively unbound forms and DAO
for data access. A potential client won't accept the Jet backend and demands
SQL Server.
I did some preliminary work and upsized my Jet tables to SQL server. I also
created ODBC links to the SQL Server tables from my front end. No conversion
of DAO to ADO.
Everything seemed to work pretty well. In fact, the app runs quite a bit
faster accessing data from SQL server than it does from the Jet backend on a
server.
So, since I would have to convert about 400 DAO recordsets, I'm not sure I
want to bother. Maybe the app would be faster with ADO to SQL Server, but it
is currently faster using DAO to SQL Server than DAO to Jet. So the point is,
it is not slower. Maybe that means nothing, but on the other hand, I think
it means I don't have an immediate problem. So why kill myself doing the
conversion.
Thoughts, suggestions are greatly appreciated.