[AccessD] On DB Bloat, Bad DB Design, and various

It didn't 'crash'.  It just stopped.  The error handler did grab it, and
safely shutdown the service.  I have no idea why I didn't set the fields to
255, I just wasn't thinking! LOL

If I walk out the door here, and they run into an error, then I get hired
back as a consultant! <grin>

Actually, error handler or not, if an error occurs, and your error handler
does nothing more then post the message, if it's an error they want to
program around, you are still going to be correcting it.  Now, if you could
write an error handler to 'fix' every possible error, let me know, that
would be a neat trick......or, it would take years to build, and megabytes
of mde or exe space! LOl.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Scott Marcus
Sent: Tuesday, May 25, 2004 12:18 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various


Drew,

I thought it was odd that your indexer would just crash (or maybe I'm not
understanding) because of size limits.

On another note about error handling:

What happens when you walk out the door (not the applications you wrote) and
there is no error handling?

You're right, you'll probably get flamed big time for admitting this, so
I'll leave you alone on it.

Scott Marcus
TSS Technologies, Inc.
marcus at tsstech.com
(513) 772-7000