Feedback by UserVoice

I suggest you ...

Create error log file for all messages but it must include enough audit info

Perhaps like a sql server log file, create a file of with error messages using err.object properties but the records must include application db, user, date/time, object(access object), module, procedure.

13 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
John shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • KVD commented  ·   ·  Flag as inappropriate

    Twenty five years ago, my work was the care and feeding of mainframes. To this day I miss the log file containing all that went right and especially all that went wrong. I know this is more on the OS side, but within Access why can we not have an error log file, much like the ldb file that comes and goes when a database is "in session". Only, if the error log file is not null, it hangs around (does not get deleted).

Feedback and Knowledge Base