G
Guest
I would like to know how to view all of access's error messages and to log
them into a table.
them into a table.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Allen Browne
Use AccessError() in a loop.
To get them into a table, OpenRecordset() and Addnew with Update.
Of course, you could just read the JET errors by creating a shortcut to
JetErr40.chm. For Access 2003, the file is typically found in:
C:\Program Files\Common Files\Microsoft Shared\OFFICE11\1033\JETERR40.CHM
To get them into a table, OpenRecordset() and Addnew with Update.
Of course, you could just read the JET errors by creating a shortcut to
JetErr40.chm. For Access 2003, the file is typically found in:
C:\Program Files\Common Files\Microsoft Shared\OFFICE11\1033\JETERR40.CHM
G
Guest
Thanx Again Allen!
Allen Browne said:Use AccessError() in a loop.
To get them into a table, OpenRecordset() and Addnew with Update.
Of course, you could just read the JET errors by creating a shortcut to
JetErr40.chm. For Access 2003, the file is typically found in:
C:\Program Files\Common Files\Microsoft Shared\OFFICE11\1033\JETERR40.CHM
G
Guest
Tru,
If you are good at VBA, check Access 2002 Power Programming by Scott Barker
for a detailed discussion of how to log errors including identifying the
modules, e.g. forms where they occur, the active control, user's name,
computer name, date/time, etc. One section also discusses logging errors to
the back end and front end of your application.
Starts on page 163.
LDN
If you are good at VBA, check Access 2002 Power Programming by Scott Barker
for a detailed discussion of how to log errors including identifying the
modules, e.g. forms where they occur, the active control, user's name,
computer name, date/time, etc. One section also discusses logging errors to
the back end and front end of your application.
Starts on page 163.
LDN