I've done a couple of something similar things to this before. One was a simple query that was run on startup (based on the logging in user) that if the query returned any records, they were advised they had x non-compliant items. The message box gave them the option to review them at that time or not. If yes, the records were presented as a locked datasheet. If not, it was a constant nag until they reviewed them (well, at least opened the query) which flagged them as having been reviewed.
The other was more complex. A pc not used by anyone but always left on ran Task Scheduler every night and updated a whole bunch of local copies of ODBC data; most of them not mine. My particular update involved a query run by the startup routine that if it found a different type of suspect data built an html email message with all of the particulars and sent an email using CDO. My db knew if the routine was being started by a regular user or by this unmanned pc.
- "doesn't work" is no help.Error #s/text do. State what's happening.
- Use code tags for code/sql; show where errors occur
Make all suggested changes in copies of your database or to its objects