Error/Audit logs and general maintenance

[Guy Kerr]

I have an ADP which is used from 6am - 10pm by approximately 35 users. I've
continued development on this product for about 3 years now so the complexity
increases and so do the errors.

As most of you know, it's hard to troubleshoot errors unless you get
specific details from users on what they were doing when the error or crash
occured. I consider myself an intermediate developer when it comes to Access
ADP's and to-date I have not really implemented much error-checking code.

Ideally I'd like to implement a way to log the errors on the client-side so
I can see what caused the error. Also, does anyone have any samples of
error-checking code I could/should include in my ADP?

Secondly, I saw a post from a MS technician that suggested cleaning up
temporary files on the client. Are there specific temp files on the client
side I should be cleaning up on a regular basis to improve or stabilize
client-side performance?

Thanks in advance

Guy

 

[Sylvain Lafontaine]

What kind of error or crash are you talking about? Like for MDB files, one
common source of problem for an ADP project is when users share a common
file for the frontend (the ADP database file) on a central file server
instead of having each one their own local copy.

If you have problems on the SQL-Server like deadlocking, this should be
solved using proper transaction isolation levels and lockings for your
procedures.

If you have bugs with your VBA code, it's hard to say what you should do.
You can search Google with terms like « vba code trapping error »; however,
adapting your application will require a considerable amount of work.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[Guy Kerr]

It's more along the VBA code error trapping that I'm looking for. I was
hoping there was an easy way for Access to generate local logs on the
workstation when an error occurs.

Each workstation has their own copy of the ADE - I'm using VS Tools 2005 for
MS Office System to compile and package the ADE.

Thanks for your response

Guy

 

[±«ÈÙÈÙ]

±«ÈÙÈÙ·¢²¼ÐÂÎÅ×éÐÅÏ¢

What kind of error or crash are you talking about? Like for MDB files,
one common source of problem for an ADP project is when users share a
common file for the frontend (the ADP database file) on a central file
server instead of having each one their own local copy.

If you have problems on the SQL-Server like deadlocking, this should be
solved using proper transaction isolation levels and lockings for your
procedures.

If you have bugs with your VBA code, it's hard to say what you should do.
You can search Google with terms like ?vba code trapping error ? however,
adapting your application will require a considerable amount of work.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)