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

Some dead horses take longer to kill than others.

Perry

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Wednesday, May 26, 2004 9:32 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various


 


I have no issue with "Can limit the field size".  I have an issue with an
arbitrary length that MAY limit valid data entry (I thought I had said
that).  If you are designing something like a state table, and the state
table will only hold US states, you can pretty safely limit the code field
to 2 characters.  It takes no time to figure that out, it takes no time to
implement etc.  Go for it.

If you want to spend your time setting fields like City to 50 characters, go
for it.  Setting it to 15 I would argue with.  Once we go there then what is
a valid value?  How much time to you spend (and bill the customer for)
figuring out EXACTLY the right amount?  What if you're wrong?

But if that floats your boat, and your customer is willing to pay for it,
then by all means go for it.

=================I read your response to Gustav just a bit OK and that
cleared up your position a great deal. It's a huge thread -- I've missed
some of it! So shoot me! ;) Personally, I wouldn't bother with field size
unless I had a specific reason to do so. 

Susan H. 

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com