-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The form's RecordSource is probably the query name, which will cause
the query's result set to be loaded into the form when the form opens.
You can change the form's RecordSource or the form's Filter to limit
the number of records that appear when the form opens.
One way is to open the form in design view & set the form's Filter to
select a record that you know is NOT in the query's recordset.
Something like this:
CustomerID=0 - if you had "CustomerID" field in recordset
and set the Filter On property to Yes. Then save the form. When it
is next opened it should open faster 'cuz it is not retrieving any
records.
Another way is to leave the form's RecordSource property blank. Then
in the AfterUpdate event of the criteria selection (a CommandButton?)
put the query name in the form's RecordSource. I'm assuming the
criteria selection is really a filter that is applied to the form.
HTH,
MGFoster:::mgf
Oakland, CA (USA)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBP7wZ2IechKqOuFEgEQJmuQCfRXGjzXc1J1m0ST5CZo4Ulo OmQ4IAoMlO
Plh31PkPXWekfRZpl9s0VmdK
=CePZ
-----END PGP SIGNATURE-----
Annette Massie wrote:
I have a database with a linked table within it.
I have a query form that opens and allows the user to select criteria
and then the form is filled with data found from the linked table.
At what point is the table linking? For example, if I open the form it
takes forever. I would like the form to open immediately, allow the
user to enter data and then have it search the linked table. It
appears it is opening the linked table and then asking for the
criteria and the processing to get the records.
I guess I was wondering how I could have the criteria form open
immediately and then have the linking take place.
Help!
