Re: when to use a function or file for information

[Loyd Goodbar <loyd@xxxxxxxxxxxxxx>]

Like Jonathan said, if you can infer the flag, just put that in a
subprocedure and be done with it.

Regarding changing files, one common practice is to have "extension" files.
Leave your myclientfile alone, and create an extension file
myclientpreferences, with fields ClientNumber, PreferenceName, and
PreferenceValue. You would populate it with
12345,'ClientLikesBiscuitsWithCoffee','Y'. This way, only those programs
that need the preference can retrieve it. The other programs are unaffected.

HTH,
Loyd

On Tue, Mar 23, 2010 at 9:35 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:

> For example : if I have myclientFile with ClientNumber and ClientType. Then
> I modifiy the file and add a flag : ClientLikesBiscuitsWithCoffee. So, I'll
> add a Y or a N to each client record. That information may be required once
> a week, although the file is being accessed all day 24/7 by multiple
> applications. If the value of the new flag could be revealed by examining
> clientType, eg clients must be red or purple, wouldn't this flag be better
> left out of the file and a service program used instead to return the value
> of the flag?