You would need some kind of login system so you know who the user is. Then you need a history table linked to the primary key of the tracked table. the additional columns would be the userid and a datetime
With this info you could find the last user to insert/modify a certain record Or you could find he last record inserted/modified by a certain user Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruce A. Chitiea Sent: Wednesday, September 04, 2013 9:19 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: COUNT = LAST and Best Practice Thanks Dennis I'm sorry, I needed to be more comprehensive, and I may not be thinking this through. I'm aware that COUNT = INSERT serves up the last record INSERTED by the user, but [ how do | can ] we provide the same service for the last record MODIFIED by the user? Appreciate the help. Bruce -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Wednesday, September 04, 2013 7:09 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: COUNT = LAST and Best Practice COUNT = INSERT Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruce A. Chitiea Sent: Wednesday, September 04, 2013 9:07 AM To: RBASE-L Mailing List Subject: [RBASE-L] - COUNT = LAST and Best Practice All: I understand from prior postings that 'COUNT = LAST' may mislead a user in a multi-user environment. The actual 'LAST' record may be "someone else's" by the time this user's routine hunts it down. What's the best coding protection to ensure that the LAST I get is the LAST I intend? Thanks much, Bruce Chitiea SafeSectors, Inc. eCondoMetrics 909.238.9012 Cell
