WalterInOz
Registered User.
- Local time
- Tomorrow, 06:23
- Joined
- Apr 11, 2006
- Messages
- 93
I have a database which holds records of publications in journals, newspapers or other media. A minority of these publications are of interest to everyone in the company. Most are of interest to smaller audiences, i.e. groups of one or four individuals. I would be surprised if the total number of users will ever be more than 30. The number of publications will be in the thousands.
the database is not very user friendly, it needs an additional feature. What I would like to achieve is to add an individual component to the database so that a person can identify records that are of special interest to him/her. This would save a lot of scrolling through records and make the publication of interest much more accessible and user friendly to each individual.
The database is split in front-end and back-end. In general, people work from the same PC all the time but there are exceptions. If possible I’d like to cater for the exceptions too, if too hard the exceptions will have to restrict activities in relation to database work to their own PC.
One way I thought this could be approached is to have a table with a field Username (based on login of the user), a field with a publicationID and a field to identify if the user has selected if that publication is ‘of interest to me’ (checkbox).
Straight forward enough? Or are there better ways to do this?
If this set-up is OK I still have a problem. This set-up requires inserting the username and the publication number into the table when the user checks the box ‘of interest to me’. This checkbox is located on a continuous form showing all records. I suspect the table tblSelectedRecords must have a double key (Username and PublicationID). Correct? If this is a viable set-up, could someone give me a leg-up what the code would look like in the after-update event of the checkbox?
thanks
the database is not very user friendly, it needs an additional feature. What I would like to achieve is to add an individual component to the database so that a person can identify records that are of special interest to him/her. This would save a lot of scrolling through records and make the publication of interest much more accessible and user friendly to each individual.
The database is split in front-end and back-end. In general, people work from the same PC all the time but there are exceptions. If possible I’d like to cater for the exceptions too, if too hard the exceptions will have to restrict activities in relation to database work to their own PC.
One way I thought this could be approached is to have a table with a field Username (based on login of the user), a field with a publicationID and a field to identify if the user has selected if that publication is ‘of interest to me’ (checkbox).
Straight forward enough? Or are there better ways to do this?
If this set-up is OK I still have a problem. This set-up requires inserting the username and the publication number into the table when the user checks the box ‘of interest to me’. This checkbox is located on a continuous form showing all records. I suspect the table tblSelectedRecords must have a double key (Username and PublicationID). Correct? If this is a viable set-up, could someone give me a leg-up what the code would look like in the after-update event of the checkbox?
thanks