>Gene,
>
>Are you fully confident that the Delete trigger (in particular) is always firing as you expect... would your program fail if it did not, or would "bad data" just start accumulating?

Heck ... our database is so full of corrupt data already ... just kidding.

It's actually working. I know there aren't orphan child records
because on SQL Selects, the orphan child records will not have
a Regional, District, or Store associated with it (these fields would
be blank).

But I program everything in a really basic style. I've done it that
way for 17 years. I've never had the crash problems that some
other people complain about. (And they have been complaining
since dBase II on CPM.) I guess I just don't push any language
to it's limit. Even VFP30 didn't crash except when it used up and
didn't release memory every 4-6 hours during development.

Gene