When using a "JET" file share, then any minor disconnecting in your network,
poor cabling, interference from machinery, or even wireless networks are all
sources that
can easily damaged a jet based file system.

You have to have a very solid high quality network to use a jet file share
system. Anything else but a high quality functioning network is going to be
subject to frequent damage to your database file.

Some sources and ways to avoid corruption is mentioned here:
http://www.granite.ab.ca/access/corruptmdbs.htm

I also explain using pictures and diagrams as to why corruption occurs. If
you are a visual type thinking person, then read the following article as it
explains why corruption occurs when you have a minor glitch or disconnect in
your network:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

"SANJAY SHAH-MICROBRAIN COMPUTERS PVT. LTD." <microbrain@vsnl.com>
wrote:

I never use cascade deletes as I prefer to handle this myself in the
few situations where this happens.

I would delete the child records and then the parent records in code.

Code something like

dim strsql as string

strsql = "Delete * from ChildTable where ParentForeignKeyID=" & _
    me.parentid.
currentdb.execute strsql, dbfailonerror

strsql = "Delete * from ParentTable where ID=" & me.parentid.
currentdb.execute strsql, dbfailonerror

Tony