From: liz@paradoxcommunity.com   
      
   Shawn,   
      
   Here's an example of what could have happened.   
      
   Referential integrity code is set up so that if you delete a parent   
   record, child records are deleted first, then the parent is allowed to   
   be deleted.  Auto-append is enabled on the form showing the parent   
   record.  The user moves past the last record of the parent table, but   
   doesn't type anything, thus, a real record isn't inserted and the parent   
   record doesn't get a key.  The user sees the blank row and decides to   
   delete it.  Code doesn't check whether the key is blank, it just assigns   
   the key to a variable, then uses tcursors to setRange on the detail   
   tables and deletes "related" child records.  Since this would result in   
   setRange including all the records in the table, all the records would   
   be deleted.   
      
   There may be other reasons - malicious, accidental, bad code or some   
   other unknown.  It's pretty hard to guess when you don't have details.   
      
   FWIW, I have not heard of Paradox tables spontaneously emptying themselves.   
      
   Are you sure they aren't just corrupt?   
      
   Liz   
      
      
   Shawn wrote:   
   > We cannot explain why a group of tables ended up completely empty yesterday.   
   > Some of the tables had thousands of records, and they all have the same   
   > modified date/time of 4pm. Most still show varying sizes up to around 2MB,   
   > but they are all empty. This software is used daily, and has been for years.   
   > Does anyone know what may have emptied a handful of tables, yet left others   
   > alone in the same directory?   
   >   
   > The company using the software is very large, and has many users tied into   
   > the database via a mapped drive. At this point, we are clueless, but we need   
   > to give some sort of explanation as to what happened. They are rectifying   
   > the situation themselves, using what they can from daily backups that they   
   > make, but from what they say, it is still quite a task.   
   >   
   > They are running PdoxRT V10 (Winxp) - It is virtually impossible to find out   
   > what/who happened due to the amount of users touching the database daily.   
   > There is a total of 121 files in that directory, and 42 were emptied   
   > somehow.   
   >   
   > TIA   
   > Shawn   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)