My Audit Trail quit working

[Guest]

I am using Audit Trail and think it works great except for one table. The
first form that I got to work in this program has decided to quit working.
It was the first successful form. After that I have incorporated 6 others
and I want to query them all for a date range to find any changed that were
made. But for that to work they need to record the changes. This first
table is not anymore after working so well for about a week. HELP!!!!!!!!!!!

Is there a max amount of forms, table, etc??

Thanks

David

 

[Allen Browne]

If you are talking about the code from this article:
http://allenbrowne.com/AppAudit.html
then temporarily comment out the error handlers so you get to see the error,
e.g.:
'On Error GoTo Err_Handler

 

[Guest]

I hate to admit it but you are talking over my head. I have learned a lot
since taking this project, but I will admit I removed the error function
because I did not understand it. Yes and am using the code listed below. It
workded for a while and then quit.

Any suggestions on reintalling the error function. So far it hasn't worked.

THANKS

 

[Allen Browne]

If the event is being triggered, and you have no error handling in place,
and something goes wrong (e.g. your temp table is missing, or the fields are
not in the right order), you will see an error.

If you see nothing, check that the relevant properties are set to:
[Event Procedure]
so the code gets called.

 

[Guest]

The error function is removed. When you modify the form nothing happens. No
error messages, just the database is modified. No audit trail either. The
proper code is in the correct [Event Procedure] also.

I am confused. It would make more sense to me if they all quit working
instead of just the one.

Thanks for the help.

If the event is being triggered, and you have no error handling in place,
and something goes wrong (e.g. your temp table is missing, or the fields are
not in the right order), you will see an error.

If you see nothing, check that the relevant properties are set to:
[Event Procedure]
so the code gets called.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I hate to admit it but you are talking over my head. I have learned a lot
since taking this project, but I will admit I removed the error function
because I did not understand it. Yes and am using the code listed below.
It
workded for a while and then quit.

Any suggestions on reintalling the error function. So far it hasn't
worked.

THANKS

 

[Allen Browne]

At the top of the procedure, add:
Stop

When it runs, the procedure will stop at this line.
Then press F8 to step through the procedure.

You can ask for the value of things in the Immediate Window (Ctrl+G) until
you debug the problem.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

The error function is removed. When you modify the form nothing happens.
No
error messages, just the database is modified. No audit trail either.
The
proper code is in the correct [Event Procedure] also.

I am confused. It would make more sense to me if they all quit working
instead of just the one.

Thanks for the help.

If the event is being triggered, and you have no error handling in place,
and something goes wrong (e.g. your temp table is missing, or the fields
are
not in the right order), you will see an error.

If you see nothing, check that the relevant properties are set to:
[Event Procedure]
so the code gets called.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I hate to admit it but you are talking over my head. I have learned a
lot
since taking this project, but I will admit I removed the error
function
because I did not understand it. Yes and am using the code listed
below.
It
workded for a while and then quit.

Any suggestions on reintalling the error function. So far it hasn't
worked.

THANKS

:

If you are talking about the code from this article:
http://allenbrowne.com/AppAudit.html
then temporarily comment out the error handlers so you get to see the
error,
e.g.:
'On Error GoTo Err_Handler

I am using Audit Trail and think it works great except for one table.
The
first form that I got to work in this program has decided to quit
working.
It was the first successful form. After that I have incorporated 6
others
and I want to query them all for a date range to find any changed
that
were
made. But for that to work they need to record the changes. This
first
table is not anymore after working so well for about a week.
HELP!!!!!!!!!!!

 

[Guest]

Thanks for the help. There was a field that somehow had gotten changed and
the system wouldn't record it. I just dont know why it wouldn't crash
completely. Anyway, its back to working. I am going to make a copy and go
through it to make myself understand what it is doing.

Again, thanks for the help.

At the top of the procedure, add:
Stop

When it runs, the procedure will stop at this line.
Then press F8 to step through the procedure.

You can ask for the value of things in the Immediate Window (Ctrl+G) until
you debug the problem.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

The error function is removed. When you modify the form nothing happens.
No
error messages, just the database is modified. No audit trail either.
The
proper code is in the correct [Event Procedure] also.

I am confused. It would make more sense to me if they all quit working
instead of just the one.

Thanks for the help.

If the event is being triggered, and you have no error handling in place,
and something goes wrong (e.g. your temp table is missing, or the fields
are
not in the right order), you will see an error.

If you see nothing, check that the relevant properties are set to:
[Event Procedure]
so the code gets called.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I hate to admit it but you are talking over my head. I have learned a
lot
since taking this project, but I will admit I removed the error
function
because I did not understand it. Yes and am using the code listed
below.
It
workded for a while and then quit.

Any suggestions on reintalling the error function. So far it hasn't
worked.

THANKS

:

If you are talking about the code from this article:
http://allenbrowne.com/AppAudit.html
then temporarily comment out the error handlers so you get to see the
error,
e.g.:
'On Error GoTo Err_Handler

I am using Audit Trail and think it works great except for one table.
The
first form that I got to work in this program has decided to quit
working.
It was the first successful form. After that I have incorporated 6
others
and I want to query them all for a date range to find any changed
that
were
made. But for that to work they need to record the changes. This
first
table is not anymore after working so well for about a week.
HELP!!!!!!!!!!!