I want to save keystrokes leading up to error 1

[TheresAlwaysAWay]

To all you brainiacs out there this may not be a difficult thing to resolve, but it's got me pulling out what little hair I have left.

Starting at the beginning, I have an Access 2007 DB front end running on SQL Server 2016 back end with about 20 users. Some have Win7 and others Win10 on their work stations.

There are instances where a user is working away and then gets an error. A lot of times it's a "The data has been changed..." error, but it could be anything. I'd like to retrace the steps that were involved in the user getting that error by saving the previous 100 (or 200 or whatever works best) keystrokes to a table so that I can literally reproduce exactly what the user did. I don't want to automate this. Just a simple button on a form that the user can click after an error occurs that says "Submit Error" would save those previous keystrokes to a table for later review.

I know that both Win7 and Win10 have keystroke recorders built in, and also there are dozens of third party apps. Can anyone figure a way to code that button so that it would save the information I want so that I can try to figure the cause of any/all of them? It can't be everything they did all day because I'd never be able to figure out where the issue was. Just a set number of keystrokes before the Submit button is clicked is what I need.

As always, I truly appreciate the help you all offer.

 

[Andrzejek]

Based on no responses to your post I would conclude that you need just a good error handler. Keystrokes may not be enough to know what had happened before an error occurred. Selection of an entry in the combo box, order of click events on your form, check/uncheck of the check boxes, etc.

You may come up with your own way – write to a table some information, and on the ‘normal’ way out of the Form, delete all records from that table for that user. When user crashes, then he would not exit the form ‘normally’ and you would have all records in the table saved. So, it would be up to you what to save in this table.



---- Andy

There is a great need for a sarcasm font.

 

[TheresAlwaysAWay]

Thanks for an excellent suggestion, Andy.

 

[Andrzejek]

If your user can reproduce the error, you may ask him or her to turn on the windows problem steps recorder, run your application, crash, and send you the file created.


---- Andy

There is a great need for a sarcasm font.

 

[TheresAlwaysAWay]

Thank you again! I wasn't aware of that feature but I certainly will look very closely at it.