Client side error logging

I thought you may be interested to know we have been using this in our production environment for almost 2 weeks now, and the results are quite interesting.

We are better able to track the database blocking much clearly than with straight SQL analysis - at SQL its hard to actually work out if a user recieved the ‘locked by another user’ error.

We are also able to identify user who need more training, or may be having issues but not reporting them. Thank you very much for your help on this.

I do however have a question for you. Is there any way we can capture more information about the users session at the time the error is logged, for example primary key of the record, where the user was, say Orders of Posted Sales Invoices, etc. I’m happy to have a play on my own but need somewhere to start, like is there a list of variables or objects that are held in memory for the user session, for example.

thanks, Mark