From: info@sundialservices.com   
      
   Kenneth wrote:   
   > I just reinstalled Windows 2000 Pro (and Paradox 9) on one   
   > of our systems.   
   >   
   > It runs the same BDE as does our other boxes: V 5.1.0.4.   
   >   
   > It has Local Share set to TRUE (as do other systems.)   
   >   
   > And its NETDIR entry reads Z:\NetFiles exactly as do all   
   > other systems.   
   >   
   > But, now, for some reason, the system with the new   
   > re-installation now gets very frequent GPFs in Paradox while   
   > other machines run fine.   
   >   
   > I read the piece including GPF information on the Paradox   
   > Community site, and based on that, ran Chimney Sweep on all   
   > of our tables (even though other systems had no trouble) but   
   > still we have the problem.   
   >   
   > What would be appropriate next steps?   
      
   Well, thank you for thinking of ChimneySweep, but when you have a repeatable   
   and isolatable issue you can be pretty sure that you are not dealing with a   
   case of file-corruption.   
      
   The first thing I would do is to look at the Event Viewer -- a system tool   
   that you may need to be an Administrator to use.  Look at all of the logs,   
   to see what might be recorded there.   
      
   Next, I would ponder exactly what FURTHER pattern might exist behind those   
   GPFs.  Set up some experiments:  particular tables?  Particular operations?   
   Also, is the application-instability isolated or general?   
      
   When you say "entering data on a particular form on a particular   
   machine ..." I consider what might be the most-likely culprit.  I don't   
   look at service-pack levels, because Paradox is pretty darned robust and   
   stable.  (That's why we all love it so...)  And it can't be the form   
   because we know that same network-resident form works fine elsewhere.  In   
   fact because it DOES "work fine elsewhere," we are pushed again and again   
   toward something much more fundamental than what has been bantered-around   
   so far.  I wish that I could conclude this paragraph with a grand   
   pronouncement of what that is:  unfortunately, all I can say is that I feel   
   my "red herring" intuition going-off.   
      
   So let's do things.  Log-off as user X and try logging-on as User-Y.  Look   
   at those darned event-logs again.  Look also at the server logs of the   
   file-server!  Act on the working-assumption that we've all been barking up   
   the wrong tree somehow.  Look for the "'DOH!' problem."  Not because any of   
   us, including yourself, are in any way silly, but because we've all slapped   
   our foreheads with great force in situations just like this.  "Screwball   
   problems..."   
      
      
   ----   
   ChimneySweep(R): Fast(!) table repair at a click of the mouse!   
   http://www.sundialservices.com   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)