And yet ANOTHER real world example - and reason why I need this.
You can't have a THAT without THIS !!!
Please examine this code (the Last Rule uses That):
Gets a Cust & builds the AddrBlock
Finds the Department, where there may be 1 or 2 Contacts assigned
Builds ContactBlock for 1st contact, if found.
Builds ContactBlock for 2nd contact, if found. (MUST use That, because there are 2 Contacts in Context)
BUT, if the 1st of 2 Dept. Contacts is UNDEFINED, then there won't be 2 in Context.
The THIS wont be there, so the THAT won't work. THAT IS THIS WHEN THIS IS UNDEFINED, ELSE THIS IS THIS AND THAT IS THAT
SO, ONCE AGAIN,
If I had a simple CLEAR CONTEXT Contacts
to use when I need it, it would turn this into a non-starter. No need for This or That here, at all.
WHY do i need the subroutine? This subroutine is used to build a temporary address & contact section which goes at the top of several different reports.
The Contacts are not even reachable from the Invoice header - they are 2 files away via a Multi reference. And in address blocks you want to remove blank lines. So rather than code that several places, I build these simple formatted blocks for displaying the data.
