Quote Originally Posted by xCav8r
Got it working now with Access and SQL Server 2000. Before I do any more, since I'm going to submit this for a KB entry, I thought I'd solicit suggestions for other information to capture. Here's what I'm currently tracking:
  • Error Number
  • Error Description (from scripting engine)
  • Call Stack (ProjectName.ModuleName.ProcedureName)
  • Line Number originating error
  • Date/Time Stamp
  • Windows Account Name
  • Message that the user saw
  • Optional message from the developer to troubleshooter
Hi,

Yepz looking good and I can't wait to get my hands on reviewing that kb entry!

I would include the Computername in my errorlog.
You could use: [VBA]
MsgBox Environ("COMPUTERNAME")[/VBA]
Depending your needs theres much more great data you can get from Environ function!

Also if you're code is spanning multiple projects I'd advice to use: Err.Source (look it up it can hold the object/project/class causing the error)

I can't think of anything else for now because you're covering so much more then I normally do. I think this entry will be very handy.

Later..