The Dreaded Application Error Message - memory could not be "read"

[goodner]

Application Error Message - .memory could not be "read"

Using Clarion 5x with Pervasive Record Manager

Have a rather large system with various accounting applications. Each child application is a separate EXE that is called by a parent or main menu EXE.The applications reside on the operator's local workstation whereas the data
is on a server drive (for multi-users). Overall the system is stable and runs well.


There are a few clients who get one of those dreaded Windows application errors when exiting one of the child applications and sometimes the parent application. The message appears similar to the following:

'such-n-such'.exe - application Error

The instruction at "0x01d122f6" referenced memory at "0x01d42390".

The memory could not be "read".

Click on OK to terminate the program.


"such-n-such" is the child application EXE the operator is exiting. They can respond and the processing continues without any apparent problems.

Recently, I have found that if an operator's data path is local and not pointing to a server drive, they can exit the applications without the error message. But, if they change the data path to a server drive, the error messages appear again. In both cases the applications being called were the
same ones on the local workstation.


Does anyone have any suggestions? I would appreciate either a "solution" or even a "work-around" to the problem. Any help would be appreciated.


Kevin Goodner

 

[ShankarJ]

Hi Kevin,

You are using a old version of Clarion which did have some issues with operating systems especially XP. Those can possibly be resolved by upgrading to the latest Version i.e. 6.3.

Anyway, since you have already idetified the problem of Network path, why don't you bypass the problem by using the SETPATH() and setting it to a local path. The error could be because of some memory leaks or invalid reference to data.

Regards