I ran into a situation where the data in several tables (not all) was completely gone. It seems that the tables that were not empty would be the ones generally open in the main application. Any ideas as to how that could happen outside of deliberate code or accidental sql statement in dbsys?

What version of DBISAM?
Are there any backup files in the folder for the tables in question ?
Have you run repair on the tables with missing data and were there any errors?

Can't say i've ever run into lost data that was not caused by corruption or similar (root cause has been external   - AV, low disk space, etc)

Raul

Raul wrote:

What version of DBISAM?
Are there any backup files in the folder for the tables in question ?
Have you run repair on the tables with missing data and were there any errors?

Can't say i've ever run into lost data that was not caused by corruption or similar (root cause has been external   - AV, low disk space, etc)

Raul

Version 4.31 b3.

We replaced the tables with backups from the night before, but to the best of my knowledge, no corruption.

Darren,

<< I ran into a situation where the data in several tables (not all) was
completely gone. It seems that the tables that were not empty would be the
ones generally open in the main application. Any ideas as to how that could
happen outside of deliberate code or accidental sql statement in dbsys? >>

I know that this is an old post, but were the tables completely okay except
for the fact that they were empty ?  In such cases, you should send the
tables to support@elevatesoft.com and we can see about retrieving the data
for you.  When DBISAM deletes records from a table, it simply marks the
space as deleted, so it is always possible to recover deleted records until
the space is re-used by new records.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com