Associated fields and @AF

[Jeff Harrison]

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

> Chad
>  
> I Know I will get lots of negative nasty notes on
> this but a few years ago we dropped all associated
> fields and created child tables. This requires some
> extra work in the automatic process but it has
> always paid off. The selection is easier, you never
> have to worry about someone needing one more
> "associated field" or having 900 blanks per record
> "in case someone needs it".
>  

[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.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and
imports.


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