M
Mark
I have read many articles and been on courses where the message is loud and
clear: Speed within Access is dependant on the less is faster rule - only
return the record/s the user wants. This makes perfect sense but I am
interested how people apply this practically. Do you have an in between
form which filters the records that will display on the target form or is
your filter built into the target form? One approach I have always liked is
to have a form in the single form view, with a combo box at the top of the
form and use the RecordsetClone and Bookmark functions to show the relevant
record. I now see that the problem with this is that all the data has been
loaded within the form as the recordsource points to a table or a query
which returns all records. What is the alternative solution? If I use the
filter property of a form is this the same as my combo box recordsetClone
and bookmark example in that all records have already been retrieved?
Thanks in advance
Mark
clear: Speed within Access is dependant on the less is faster rule - only
return the record/s the user wants. This makes perfect sense but I am
interested how people apply this practically. Do you have an in between
form which filters the records that will display on the target form or is
your filter built into the target form? One approach I have always liked is
to have a form in the single form view, with a combo box at the top of the
form and use the RecordsetClone and Bookmark functions to show the relevant
record. I now see that the problem with this is that all the data has been
loaded within the form as the recordsource points to a table or a query
which returns all records. What is the alternative solution? If I use the
filter property of a form is this the same as my combo box recordsetClone
and bookmark example in that all records have already been retrieved?
Thanks in advance
Mark