Associated fields and @AF

[Jeff Harrison]

--- Christopher Yerry <christopheryerry at yahoo.com>
wrote:

<top posting fixed>

> Jeff Harrison <jeffaharrison at yahoo.com> wrote:
[snip] 
>> I'm going to guess you won't get too many nasty
>> notes
>> on this one. I agree that in most applications that
>> child tables are the way to go. However, there are
>> applications that are simple enough, where I
believe
>> that associated fields are the way to go. As Jay
>> mentioned, It eliminates the need for much code
that
>> would otherwise be necessary. In simple
>> applications,
>> this can save you quite a bit of time.

> Every simple application you take a shortcut on will
> be found by someone who will base a huge system on
> it; (and then want you to fix it!)
>  
> cy
 
Shortcut vs. overkill.  As in most things it is not
black and white and requires a judgement call.  You 
should not use an atom bomb to kill an ant hill.  I
think that you should use the amount of fire power
that is appropriate, and leave a reasonable amount of
room for growth.  Otherwise you are doing the customer
a dis-service.

If it later turns out that you need to re-write all or
part of the application, then you hopefully will be
able to bill the client!

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHImport and JHExport. The fastest and
easiest ways to create code for filePro Imports and
Exports. 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com