Proper syntax for email function including a repeat region

Question

Hey Guys, a fellow ADDT developer and myself ran into a odd challenge recently and was wondering if someone knew a shorter answer.
LET ME BE CLEAR..I’m not looking for a suggestion, we have resolved the problem..we ARE LOOKING FOR PROPER or shortest FORMAT.
(we used a submit redirect to a php page that used the “Send Page Section”  and then redirected back..the email looks great)
This may be a mood point since ADDT is going away but, until then, we feel this will be an useful post because quite often you may have multiple products to email from your SQL statement.
With that said. We used the send email function on submit.
1.       Our email content was a HTML content file. Since it was not a php file our repeat region obviously did not work.
2.       We substituted the HTML file for PHP (just for giggles)..no joy
3.       We tried regular content as a string..no joy
We know how to get single rows with the  {table.column} format…but we need to list all undetermined number of products/rows.
So how would the string or function re-write look  if you needed a repeat region.
EX:
emailContent (“ this” . ‘does’. “work”);  regular string
emailContent (“ this” . $var   . “work”);  regular string
emailContent (“ this” .   do{  $row; } while( xxx = xxx)  . “work”);  DOES NOT WORK
emailContent (“ this” .   while( xxx = xxx)  {  $row; }   . “work”);     DOES NOT WORK
I assume the conflict is you can’t have a function like DO or While in the string….but I also can’t use a php include file.
There must be a shorter, cleaner syntax that won’t require an advanced set of arrays or for each???
so  how would a nice clean example of  repeat region results  inside email content, or include file for email contnent, look?
Thanks

Answer 1

David, in theory I agree with you, but to a large degree I am completely changing the logic of my human interface. My existing code pre-processes the raw data and saves the results to disk for any future usage. 
It can then rapidly rebuild all pages for the entire Intranet site when your personal view of the data is changed. 
After the full creation of all pages, the fixed pages can be viewed using your browser. 
When you want to change your view, you run the code which completely rebuilds every Intranet page.
My new software will approach the data differently.  My raw data will be stored with no pre-processing. The pre-processing will occur as the user changes dates and the pages will be built individually on demand, one at a time.
The second phase of my Windows Form app will be to create pop-up windows that allow the users to modify the definitions for their custom views of the market. 
When a view is changed, the software will be able to pre-process, as needed, the current date’s data and rebuild the current page with any new changes.
I intend to create a Refresh.cpp file.  The various segments of the Form’s code will set variable such as date change, view changed, watch list changed, etc. and then call Refresh(). 
The refresh code will then be able to do the minimum recalculation necessary to rebuild the proper HTML stream. 
This is another reason to break up the code into various cpp segments such as: LoadRawData, RecalculateViews, BuildPage, etc.
PS: David, I tried to send you a personal e-mail using your home page link. 
Hope that was OK and not against forum rules!