[AccessD] Missing records

John,

The first thing to do is examine the relationships for the tables missing
records.  If "cascade delete" is turned on (a NO-NO in my humble opinion)
then deleting a single record (such as a customer) will (after a warning of
course) delete ALL child/grandchild/...greatgreatgreat records.  

Let's say that a client has invoices and invoice line items.  Yep, all gone.
Repair service calls / line items?  Yep, all gone.  Payments?  Yep, all
gone.

Cascade delete of a single (for example) customer record WILL delete all
child records, however far down they go.  Potentially dozens or even
thousands of records, all gone because the user was "just deleting a single
customer record".

I pretty much design my databases to never turn on Cascade delete, and then
build delete queries tied to buttons which only supervisors can see/click.

John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark
Sent: Friday, February 03, 2006 9:51 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Missing records

We got a call from a department that has a small Access 2K db.
"Something" has happened, and they are missing about a quarter of their
records. This was being investigated by a technician and I was just asked
the following question:

If a PC is "hard-booted" can an Access DB lose records w/out showing signs
of corruption (i.e. the db still runs)?"

I really don't know the answer to this question. I have had nearly no
experience w/db corruption, since starting with Access 5 years ago. I used
to use FoxPro...there are still some old FoxPro 2.6 (DOS) dbs hanging around
actually...and corruption was a huge problem w/them.

Anyone got any tips on this?

Thanks!

John W Clark
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com