From: Info@KennedySoftware.ie   
      
   Kenneth,   
      
   > "The exception generated was c0000005 at address 4CE1036B   
   > (OsLdMBRisCJKKana)"   
      
   That c0000005 error is a fairly common one, and sometimes difficult to   
   identify exactly, and, therefore, to eradicate. I've seen it!   
      
   I suggest some coffee... and Google on it...   
      
   See how MEMTEST goes, but, I've seen cases with memory that passed   
   MEMTEST, but was not suitable for the motherboard, and failed randomly   
   during normal (stressful) use of the PC. Cause: the RAM sticks were   
   "buffered", and the MB was designed for non-buffered. With high   
   activity, the actual buffering ICs heated, and caused nasty problems.   
      
   Any chance you have "identical" PCs, whereby you could swap around the   
   memory sticks?   
      
   Try killing all unwanted services before running the PDox app, in case   
   some other "app" is conflicting with your form.   
      
   Check that all updates have been applied to the OS itself.   
      
   What about local disk-space?. I think c0000005 sometime triggers on low   
   free-space.   
      
   Can't think of anythin' else right now!   
      
      - Mike   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)