"Does your report define all of the field specs for the record layout and
compare the 'before' fields to the 'after' fields to find what has been
No. I use data structures.  For example

a) Read Inhouse Journal Data (until *EOF)
   When you read a record, the data will be automatically in the three 
data structures you defined, let's say:
   2) AFTER_DS

b) Select action, depending on journal entry type:
   1) Record Added  "PT" (Print the data from RECORD_DS)
   2) Record Deleted "DL" (Print the data from RECORD_DS)
   3) Record Updated 
      i) Print "UB" (Print the data from BEFORE_DS)
      ii) Print "UP" ((Print the data from AFTER_DS)

"For new records, do you print every field on the report?"
What I do, based on the previous example, is that I use only the fields 
that the clients want to check if they are different: a name, a code, etc. 
 If that is the case, I print it.  If not, I do not.  If you have a record 
UB and UP, you have a record that was definitively changed but not 
necessarily the field you are auditing in. 

Hope this helps,

Peter Vidal 
PALL Corporation / SR Programmer Analyst, IT Development Group
10540 Ridge Rd., Ste 203, New Port Richey, FL 34654-5111

"If an idea's worth having once, it's worth having twice."
Tom Stoppard (1937- )

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.