I can't help it, I have to reply on this post otherwise my signature doesn't mean anything

 

If you get the error Windows will generate a report of the error. Maybe you can locate where the error occured and maybe CodeJock (if the error is caused with CJ controls) will recognize something in the report that will help solving the problem.

 

If the error occurs several times a day your users won't be happy and you have to tell them that you don't have a solution  Well good luck with your quest.

 

I am using CodeJock 11.1.3 with Progress 10.1B.   From time to time our users crash with a 'memory cannot be read' error.  There is absolutely no pattern to this and it is proving very difficult for me to find the cause.  We make use of the CodeJock Commandbars, Docking Pane and ShortcutBar within our Progress application and I have a feeling that these comntrols are somehow involved in this ereror (we did not get the error with an earlier version of our application which did not use CodeJock).

 

I don't expect anyone to come up with a solution for me from this very poor description, but I was just wondering if anyone else had encountered something similar and whether anyone might be able to point me in the right direction?