George-Bowyer
Registered User.
- Local time
- Today, 07:03
- Joined
- Dec 21, 2012
- Messages
- 178
In the past, my db has tended only to be used by one person at a time.
So when a user wants to mark a group of contact records to be dealt with for some reason, I have just had a "fldMark" checkbox field on each record that the user can check either individually on the forms or in groups by queries; then do whatever operation on "qryMarked" and then uncheck them all.
I am now getting to the stage where I am likely to have multiple users wanting to work with different batches of marked records - so all trying to use the same checkbox is obviously a non-starter.
I am planning to address this by creating a "tblMarked" with fldContactID and fldUserID as a dual key (to avoid any risk of duplications).
Then when the user selects ("marks") the contact by whatever means, this will be recorded by writing new records to tblMarked, which will then be stored, regardless of what other users do, until they are deleted when the user "unmarks" the records.
I can think of a number of other ways of going about this, but all involve too many tables or checkboxes, so I think this will be the best method.
If that all makes sense, am I on the right lines?
Many thanks,
George
So when a user wants to mark a group of contact records to be dealt with for some reason, I have just had a "fldMark" checkbox field on each record that the user can check either individually on the forms or in groups by queries; then do whatever operation on "qryMarked" and then uncheck them all.
I am now getting to the stage where I am likely to have multiple users wanting to work with different batches of marked records - so all trying to use the same checkbox is obviously a non-starter.
I am planning to address this by creating a "tblMarked" with fldContactID and fldUserID as a dual key (to avoid any risk of duplications).
Then when the user selects ("marks") the contact by whatever means, this will be recorded by writing new records to tblMarked, which will then be stored, regardless of what other users do, until they are deleted when the user "unmarks" the records.
I can think of a number of other ways of going about this, but all involve too many tables or checkboxes, so I think this will be the best method.
If that all makes sense, am I on the right lines?
Many thanks,
George