Re: Same form, but one system GPFs...?

Kenneth,

The Dr. Watson error message means nothing to me too.

Sometimes, if a Paradox Form or Library was compiled and saved with the 
"Compiler Warnings" and/or "Compile with Debug" options checked... you can

experience erratic errors or GPF errors.  Try opening the Form and or 
Libraries it calls in Design Mode and check if these options are checked. 
If they are checked then uncheck them then compile the file again and save

it.  Do this for the Form and any Libraries that it might open.

If that doesn't solve the problem and no one else jumps in with another 
idea... then I would consider the idea that possibly there is a corrupt 
file(s) within either the Paradox installation or the Windows OS 
installation.... or you are experiencing an intermittent hardware failure.

I would first consider the easiest approach by removing Paradox 100% from 
the PC then re-installing it from scratch.  Make sure to add any updated 
Service Packs to Paradox after re-installing it and reconfigure the BDE so

it's identical to other PC's (of the same OS) that are known to work. 
Make 
sure that access rights are set high enough for the required Paradox 
directories.

If that doesn't fix it, I'd then consider the idea that the Windows OS
might 
have corrupt files and possibly re-install it...   The best results is to 
reformat the drive and install Windows from scratch...  This is a "Drastic

Action" and may require considerable time and pose the possible loss of 
critical programs and data.  You will need to get ALL the service updates 
for Windows from MS, etc. etc...  :((

Before you do any of these things... hopefully someone else here will jump

in with a less aggressive solution and save you the headaches involved
with 
my suggestions.

My reasoning is this... if all things are equal (the PC's settings are 
identical to working PC's with the same OS) and you are still getting GPF 
errors on the one PC... then the problem is either corrupted files or 
failing Hardware.

An example of failing hardware....  I've seen problems like this because
of 
a failing CPU fan...  The fan was still spinning, but not fast enough to 
keep the temperature of the CPU cool enough...  The over heated CPU caused

error messages and corrupted file writes to the HD.  After replacing the 
fan, the errors went away.... but the OS files by that time were minced 
meat... I had to re-install the OS.    My suspicions were directed towards

the CPU fan after I noticed the audible sound of its failing bearings.

For your sake... hopefully someone else here has a better idea and you
will 
not be faced with re-installing Windows.


-- 
 ...
    `·.¸¸.·´¯`·.¸¸.·´¯`·->  rodney