AW: How to treat obsolete information from a physical file

Hi,

we are normally using History Files, that means as soon as an client gets
inactive or an order is completed, the data get copied into the history
files and deleted from the "active" files. The history files have the same
fields in the same sequence as the original files.

If we need both active and inactive rows, we use SQL views that merge both
files with an UNION clause.
In this way we keep the active files relatively small and have to use
exceptionally the whole bunch of data.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von David FOXWELL
Gesendet: Friday, 06. November 2009 12:17
An: RPG programming on the IBM i / System i
Betreff: How to treat obsolete information from a physical file

Hi,

I'd like to know how you are treating such records, for example, a client
that is no longer with you. In our client file, the client would be flagged
as being no longer active, but never deleted. The trouble is, this has led
to us creating logical files that omit these inactive records and that is a
problem for the programs that use SQL.

Now, my RPG program needs to list clients in a subfile where the user types
part of a name and/or town. If I don't use the OMIT logical, then my program
must read all active and inactive clients then do the same with the address.

Any thoughts will be appreciated.