Actually, I want to talk about this message. This message does not make any sense to me. Also I am sure, If I send this over to the programmer. It might take ages to tell where exactly problem is.

Many programs I see out there have their own error trapping. And user-friendly messages.

I think it will be a good idea to start working on this also, as part of DE8.5. Just to point the developer to a place where the problem is. Rather than us programmers, need to open up pretty much everything to see where the problem is. That means, time wasted :-(

Regards
Arul

Hi Arul.

I think we have talked about this message a lot before ;-)

You can talk as much as you like but there is nothing anyone can do about this message.

DataEase obviously have error trapping too, this is not part of that.

This is Windows (The Operating) system that protects itself.

DataEase for WIndows was developed with unprotected binary code which was necessary back then to get it fast enough.

The problem is when any part of the code point outside its allocated memory it will trigger windows to throw a GPF.

The way to fix this is not by any error trapping, but by improving the code so it won't point outside it's allocated memory. 

We have done a lot of this but it will be close to impossible to find and weed  out them all, especially if you try OML and all that stuff into the equation.

The only way to get around this is to rewrite the entire product, and as you know we are doing that too but as long as there is a DFW derived product (DE8 etc) we will never get completely away from the GPF.