[AccessD] Re: Normalizing issue

Susan,

 John made and excellent point (pay check).  There is also that always fine
line of what a client really needs vs what they can really afford.  As long
as everyone is aware of the limitations that will be imposed by a particular
design, then "best" is not always "better".

<<I think I'm going with one table. Tomorrow, I may change my mind. :)>>

  That's what I'd do<g>.  I also leave design notes within the app on why a
given approach was used and how it could have been made better.  That helps
who ever maintains it down the road understand why it is the way it is.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
Sent: Friday, June 24, 2005 11:11 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Re: Normalizing issue


This is pro bono -- no paycheck. :) I'm also doing it in my spare time -- as
I can -- so there's no time pressure. Ultimately, I will be the only user
unless other regions decide they like it too. Everything I do for me -- but
I do need to keep in mind that it might grow -- it's a consideration.

I think I'm going with one table. Tomorrow, I may change my mind. :)

Susan H.


While also keeping in mind just how much you are being paid to do this
job...


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