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

>Single table query on a table with all 255-char text fields returned a
"query too complex" error.

Interesting.  Is this a known bug?  How did you discover that was the issue?

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Monday, May 24, 2004 2:02 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various


Single table query on a table with all 255-char text fields returned a
"query too complex" error.

Charlotte Foust

-----Original Message-----
From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com]
Sent: Monday, May 24, 2004 9:10 AM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various


Actually, I would say that relying on Jet to do data validation is lazy
programming, not the other way around.

Lets say you were storing State abbreviations.  So you limit your field size
to 2.  Why limit the field size, when you can just force data entry through
a combo box (or even use a lookup field...LOL, sorry, couldn't resist). When
the US takes over the entire world, we may have to go to 3 letter
abbreviations.  When that happens <evilgrin>, if you have limited your
field, you now have 2 changes to make, instead of 1.

Once again, I've been burned quite a few times by other people's field size
limitations, and I have NEVER been burned by fields being set to 255.  Just
out of curiousity, how did the 255 character fields bite you in a query?

Drew