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

And I do use a lot of memo fields (with all the inherent problems) when I
suspect that more than 255 will be needed.

John W. Colby
www.ColbyConsulting.com

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


I know that I jumping in the middle but...

By setting the field to 255 aren't you still imposing a limit. Why not set
it to memo to be safe? (playing devils advocate) I know there are reasons
not to set to memo and I'm not suggesting you do so. I'm just pointing out
that maybe you setting it to 255 is going to get you burned in another way
down the road. Don't ask me what other way because your reasoning for
setting it to 255 is for things unforeseen. I understand where you are
coming from. Like Brett I'm just surprised hearing that you do set it to
255.

Not arguing (maybe I'll start setting mine to 255), just thinking of the
flip side.

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