[AccessD] Cascade-delete (was: Estimating Help)

Hi Drew

> I know what you are saying though, so I can't argue the logic.  However, I
> would be far less resistant to letting a Server side DB do things like that
> for me, then a Client Side db.  Don't get me wrong, I love Access.  In fact
> I like to push Access to the limits, and beyond when I can get away with it.
> However, in doing so, I need it to be lean.

If you are talking about a Jet backend, how can it be more or less
"lean"?
The frontend or middle-tier will be more lean if you let the backend
do the dirty work it is designed for.

> I certainly have NOTHING against using tools like RI, or bound forms, etc.
> In fact, on occasion, I use them myself.  However, most of the stuff I do is
> designed for relatively heavy use, so I keep Jet doing only data
> reads/writes.  I don't want it doing anything else.  But that is just the
> stuff I am working on.  Everyone has their own 'markets' or customer base,
> and thus their own development 'traits'.

That's your choice, of course. I'm not quite sure, however, what
"heavy" means? Is it size or multiple connections (users)? In that
case I see no idea in not letting the Jet engine do the heavy work it
is designed for; actually you'll experience that it - when RI is
enforced - will work faster when you do operations on related tables.

/gustav