G
GaryG
I am working in Access2000 with .mde front-ends on client workstations. A
challenge I'm face is tracking down unusual errors on events. In the
'master' database, when I am creating/verifying VB code, I use the
debug.print and immediate window to see the code in action as I go along. At
the .mde level, this is not possible. I HAVE been simply placing a text box
on the form, and taking the debug.print statement and replicating it to the
text box to show the 'current-step' the user is on, as well as to show error
messages if one is encountered. What I would LIKE to see is a logfile of all
steps each code is running through. This way, I can see the entire picture
of what happened instead of the last step run. When I try to do this with a
text box, it will not accept the New Line (chr(10)) code, so I get "step 1:
Add record Step 2: update combo Step 3: Get Value" etc etc. Not very
readable! I know I can create a text file, but that would be very
cumbersome, especially with 30+ users in the same database. Any suggestions
would be helpful!
challenge I'm face is tracking down unusual errors on events. In the
'master' database, when I am creating/verifying VB code, I use the
debug.print and immediate window to see the code in action as I go along. At
the .mde level, this is not possible. I HAVE been simply placing a text box
on the form, and taking the debug.print statement and replicating it to the
text box to show the 'current-step' the user is on, as well as to show error
messages if one is encountered. What I would LIKE to see is a logfile of all
steps each code is running through. This way, I can see the entire picture
of what happened instead of the last step run. When I try to do this with a
text box, it will not accept the New Line (chr(10)) code, so I get "step 1:
Add record Step 2: update combo Step 3: Get Value" etc etc. Not very
readable! I know I can create a text file, but that would be very
cumbersome, especially with 30+ users in the same database. Any suggestions
would be helpful!