K
karen scheu via AccessMonster.com
I have two forms. The first contains filter selections. When View button
is selected, I check the filter selections and build a Where string. Then I
open the second form as follows:
DoCmd.OpenForm "Frm201Main", , , strWhere.
On the second form I have a button that opens a third form which allows users
to update comments. When the user saves the comments, he should return to
the second form and the changes appear on the second form. In order to get
the changes to appear dynamically, I have to requery the second form. My
question is that if I simply do a .requery on the form and the form's record
source is a query that contains all the data instead of the filters that were
used when the form was opened, won't the performance be bad? It seems slow
to me, but I don't know how to handle this. Should I be setting the record
Source of the form dynamically instead of opening it with a where string?
Thanks,
Karen
is selected, I check the filter selections and build a Where string. Then I
open the second form as follows:
DoCmd.OpenForm "Frm201Main", , , strWhere.
On the second form I have a button that opens a third form which allows users
to update comments. When the user saves the comments, he should return to
the second form and the changes appear on the second form. In order to get
the changes to appear dynamically, I have to requery the second form. My
question is that if I simply do a .requery on the form and the form's record
source is a query that contains all the data instead of the filters that were
used when the form was opened, won't the performance be bad? It seems slow
to me, but I don't know how to handle this. Should I be setting the record
Source of the form dynamically instead of opening it with a where string?
Thanks,
Karen