[AccessD] Which is faster DAO or Append Query? (in this case)

 If your doing this to allow for row selection in a continuous form, there
is a way not to pre-populate the temp table and do it on the fly.

 Change your join to an outer join, then bind the control to:

=Not IsNull(<selection table>.<PK FIELD>))

  You can then lay a transparent command button over the indicator to toggle
the state by inserting/deleting records in the selection table.

  There is another variation of this as well where you can bind the control
to a yes/no field in the selection table and let the user edit the control
directly.  Row fix up will automatically add the record if it's not there.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, December 19, 2013 11:16 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Which is faster DAO or Append Query? (in this case)

Dear List:
 
I have a form which is bound to a temp table.  When the form is opened, the
temp table records are deleted and re-created with an append query - two
tables and two queries linked up.  It appends 36 fields.
 
The user reports 5-10 seconds delay opening the form and it is due, AFAICS,
to the append query.
 
I have always done a lot of stuff in DAO and find it to be easy to write and
fast in its operation.  So I could do this in DAO but would it be any
faster?
 
MTIA
 
Rocky