Doug Steele
dbdoug at gmail.com
Tue Mar 13 12:20:29 CDT 2012
John: I came across this blog post today; it may be of interest to you regarding ADO: http://accessexperts.net/blog/2012/03/13/why-using-unbound-forms-are-a-bad-idea Doug On Mon, Mar 12, 2012 at 7:32 AM, Dan Waters <df.waters at comcast.net> wrote: > I haven't tried using a recordset as the source for a form. But, I think > that you would need to assign the recordset to the form's Recordsource > instead of the form's Recordset. > > I typically assign a table or query to a form's Recordsource. Then I can > use the form's recordset to read, update, or delete. > > Dan > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Monday, March 12, 2012 8:00 AM > To: Access Developers discussion and problem solving > Subject: [AccessD] Me.Requery doesn't work with ADO bound forms > > I am learning the ways of ADO recordset bound forms, IOW creating > ADO.Recordset objects and assigning that to me.Recordset. It is common in > DOA bound forms to just do a me.requery whenever you want to requery a > form. > AFAICT that no longer works, AFAICT it doesn't do anything. > > Me.recordset.requery does does in fact requery the form however it leaves > it > with a #Name in every control. So far I am having to rebuild the ADO > recordset object from scratch and assigning the new ADO.Recordset object to > me.Recordset to get this to work. > > -- > John W. Colby > Colby Consulting > > Reality is what refuses to go away > when you do not believe in it > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >