Re: when to use a function or file for information

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

David

If a second field in a file is dependent on the value of another field 
in that file, that seriously violates normalization, if I remember 
rightly. The other way to do it is to have a file comprising the first 
value and the flag only, then either JOIN to that or CHAIN to that - no 
hard-coded values.

Vern

David FOXWELL wrote:
> > -----Message d'origine-----
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Loyd Goodbar
> >
> > Like Jonathan said, if you can infer the flag, just put that 
> > in a subprocedure and be done with it.
> >
> >     
>
> So, if the flag were dependent upon say, the client type, I could have :
>
> clientFlag = getClientFlag ( clientType )
>
> and in getClientFlag :
>
>  If clientType = TYPE_THIS....etc
>  If clientType = TYPE_THAT....etc
>
> But this is seen as 'hard-coding' the client type and seems to be discouraged here. Hence the preference for adding the flag to the client file.
>