M
mscertified
I'm dealing with a heavily used multi-user database. Currently the main form
allows filtering and uses the ApplyFilter command to change the recordset.
I'd really like a design that reads/holds only ONE record at a time.
So could I somehow create a recordset of the primary keys of the ApplyFilter
results, then manipulate the filter to "WHERE ID = <primary key" to retrieve
only the single prev/next record based on the primary key? I guess I'd have
to replace the Access navigation buttons with my own custom navigation
buttons. The current code makes heavy use of the 'on current' event, would
this be affected? Do you think this would be an improvement in design?
allows filtering and uses the ApplyFilter command to change the recordset.
I'd really like a design that reads/holds only ONE record at a time.
So could I somehow create a recordset of the primary keys of the ApplyFilter
results, then manipulate the filter to "WHERE ID = <primary key" to retrieve
only the single prev/next record based on the primary key? I guess I'd have
to replace the Access navigation buttons with my own custom navigation
buttons. The current code makes heavy use of the 'on current' event, would
this be affected? Do you think this would be an improvement in design?