All,
As I'm working through an odd locking issue (separate post), I'm wondering if it is best (or at all beneficial) to employ snapshot RecordSet types (on forms) - specifically where I would never need to update information.
The Scenario:
I have a search form where the search criteria fields are contained on the parent form and the results of the search are contained on a continuous subform. From my reading, I understand that setting the subform (in this instance) recordset type to Snapshot is ideal where the data will not need to be updated (perfect for a search form).
Aside from holding less in memory, (the snapshot is just that - a snapshot of the data at a given point in time), I'm wondering if this might possibly alleviate another problem I have where RunSQL statements are encountering a locked record issue.
I'd love to hear your thoughts and experiences with using the Snapshot RecordSet Type on forms. Reasons, Do's, Don'ts, and strategies.
Thanks!
Gunner
As I'm working through an odd locking issue (separate post), I'm wondering if it is best (or at all beneficial) to employ snapshot RecordSet types (on forms) - specifically where I would never need to update information.
The Scenario:
I have a search form where the search criteria fields are contained on the parent form and the results of the search are contained on a continuous subform. From my reading, I understand that setting the subform (in this instance) recordset type to Snapshot is ideal where the data will not need to be updated (perfect for a search form).
Aside from holding less in memory, (the snapshot is just that - a snapshot of the data at a given point in time), I'm wondering if this might possibly alleviate another problem I have where RunSQL statements are encountering a locked record issue.
I'd love to hear your thoughts and experiences with using the Snapshot RecordSet Type on forms. Reasons, Do's, Don'ts, and strategies.
Thanks!
Gunner
Comment