[AccessD] Updateable Access Forms Bound to ADO Recordsets

 I don't think it's a case of "must" any more, although it was in Access
2000.  I haven't had occasion to work with ADO in Access since moving to
XP and then 2003, so I can't say whether bound forms work right or not.


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Saturday, December 23, 2006 8:01 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Updateable Access Forms Bound to ADO Recordsets

Hi Jim,

This OLEDB Provider could be used with an mdb as well as an adp
(especially with SQL Server 2005 Express using Management Studio).
Also, I think I read that Access 2007 can be used as an ADP with SQL
Server 2005, but could also used with SQL Server 2000 in some sort of
'crippled' mode.

All the discussions in this list seem to state that if you're using ADO
you must use unbound forms, and bound forms are recommended for DAO/Jet
but unbound forms could be used.

This OLEDB provider:

	.provider = "Microsoft.Access.OLEDB.10.0"

describes using bound forms with an ADO recordset.  

I have a currently working mdb database using DAO/Jet in one location
that my client wants to have installed at various plants in North
America.  All these plants are on the same WAN, so a switch to ADO is
completely feasible.
But, my system has about 25,000 lines of code where all forms are bound.
If I can use essentially the same system connected to ADO, I can switch
over with a minimum of code rewriting and become much more valuable to
them in the long term.

My plan is to use Access 2003 (mdb) with SQL Server 2005 Express with
Management Studio Express using this provider.

Dan Waters

-----Original Message-----
Subject: Re: [AccessD] Updateable Access Forms Bound to ADO Recordsets

Hi Dan:

I have done most of my Access work with direct ADO-OLE connecting to MS
SQL and Oracle databases since 1997. Performance increases are on
another magnitude. 

Some jobs that would take an hour could be reduced to seconds by not
using pass-through queries, ODBC drivers... and never using DAO MDB
databases except to stash temporary local data.

Note; that the MS article is describing an ADP type database and as far
as I know that technology has a tenuous future... though my knowledge on
its survival may not be current or complete and some other member may
have further comment.

HTH
Jim

PS I have rarely used bound forms     

-----Original Message-----
Subject: [AccessD] Updateable Access Forms Bound to ADO Recordsets

MS has published a seven page KB article on using updateable Access
forms bound to an ADO recordset.  This uses a specific OLEDB Provider
with A2002 or A2003.  The article discusses requirements for SQL Server,
Oracle, and ODBC databases.

Has anyone tried this or have any thoughts on what the performance might
be on a WAN?

http://support.microsoft.com/kb/281998


Thanks!
Dan Waters