The positional value of a options list can be determined by the value of a specific 'repeat' cycle. If you have told Pathagoras to repeat a block 4 times, on the first round, it will return the first in the list of options, second round, the second item, etc. This is similar to the way a MailMerge builds a series of documents from each item in a database.

   If you have a 'reciprocal' document (one prepared for two people with the primary actors reversed -- think simple Wills), you can, with a single action prepare both documents, reversing just the actors are needed.


   The action is performed by combining a <<*Repeat* block (to control, obviously, the number of documents being prepared) and an <<*Options(increment)* . . . >> block nested inside. As each repeat is implemented, the appropriate Option in the list of options is inserted. You don't need to make a selection in this scenario. The selection is simply the nth item, marrying up with the repeat cycle.

   By way of (a bad) example, let assume the following setup:


<<*Repeat*How many letters?*

 <<*Options(increment)*Mr. Robert Smith/Mr. John Jones/Ms. Mary Marshall/Susan Adams>>

 <<*Options(increment)*123 Main Street/765 Oak Tree Lane/332 Lands End Circle/432 Mason Street>>

 <<*Options(increment)*Jacksonville, FL  32211/Savannah, GA 31776/Houston, TX  44598/San Reno, CA  98876>>        


 Dear <<*Options(increment)*Bob/John/Mary/Susan/Robert>>,


 Thank you for your order of <<*Options(increment)*apples/bananas/cherries/dates>>





   If you selected 4 as the value of the Repeat, the result would be 4 letters, one addres to Mr. Smith (Bob), thanking him for ordering apples; one addressed to Mr. Jones (John), thanking him for ordering bananas, and so forth.


 Now, even though the above is illustrative of the action, as a practical matter, you are not going to pre-list all your names, addresses and products as shown above (which is why we described it as a 'bad example'). You are likely to use a database. Currently the database is linked to your Alias lists. (More data linking will be possible in the future as we see this function being used more in real life. So, if your alias list contains the values for the various items, a letter that looks like this can be processed.

<<*Repeat*How many letters?*


 <<*Options(increment)**Street Address*>>

 <<*Options(increment)**City, ST  ZIP*>>        


 Dear <<*Options(increment)**FirstName*>>,


 Thank you for your order of <<*Options*(increment)*product ordered*>>





 Another practical application of this feature is a pair of documents that are reciprocal in nature. An I Love You Will, and similar documents that have identical substance, but with the actors reversed in the two documents are good examples. Just prepare the <<*Options . . . " choices to reflect the appropriate cycle (first or second) and the respective positions of values and/or variables.



<<*Repeat*Last Will and Testament of

<<*Options(increment)*[HUSBAND NAME]/[WIFE NAME]>>

I, <<*Options(increment)*[Husband Name]/[Wife Name]>>, being of sound mind, make this document my Last Will and Testament.

   1. I give all of my property and estate to my <<*Options(increment)*wife/husband>>, <<*Options(increment)*[Wife Name]/[Husband Name]>>. If my spouse does not survive me, then I give my estate to my children, <<*Repeat*Number of Children?*[Child].>>

   2. I appoint my <<*Options(increment)*wife/husband>>, <<*Options(increment)*[Wife Name]/[Husband Name]>>, to be my Personal Representative.



<<*Options(increment)*[Husband Name]/[Wife Name]>>



======Page Break=======




Created with Help & Manual 7 and styled with Premium Pack Version 2.70 © by EC Software