Quote:

I am not sure if I understood you properly. I find FormAsDialog very useful and use it quite extensively. FormAsDialog is very powerful tool for user interaction. I believe you did not use it that much as you indicated earlier and you did not use ClientLocalValue ( ) command before. You use ClientLocalValue ( ) command to take the value from the form to the Dialog form and dialog form has all sBasic commands available to it. I usually use process button just to close the Dialog form and that gives to the string of all the values from the Dialog form.  Dialog form is for user interaction only.

Hi Bharat,

You're correct - I haven't used @FormAsDialog before.  But this calc I'm programming is to alert clients - most of the clients will receive this alert via email (by @sendmail), and that part works beautifully.  For the clients without email (or at least don't want alerts delivered to them via email) I must print the alert and then fax the printed alert to them.  There may be 50 or 80 alerts to print and fax.  If I 'writeln' the alert, then I can print each alert (with different client info on each one) individually, but that is too tedious to contemplate on a weekly basis.  And the same variable that displays so perfectly with writeln, I'm having trouble with Printstring printing the same variable.   Printstring is so tedious it makes me want to pull my hair out, and I am resisting the anticipated hours of trial and error I'll need, just to print some simple text on a sheet of paper.   So I thought, well maybe I can make a new Form for my Client database (the new form just having 3 unbound fields - Client name, Client fax#, and a big editor text box to paste in the alert data), I could have code call it up, load it, then use PrintForm to print that FormAsDialog, then throw it away and move on to the next loop.   here is an example of the simple text alert that I need Sesame to print automatically.  Heretofore, PrintString just prints the header, but none of the product data lines, although the messages email beautifully.  I was trying to think outside the box a bit. 

Actually, maybe just making a new form (ClientFax or some such) for Client database, and put the command button to run this calc in that form is my answer.  All of the calc is done with XResultSet commands, so maybe XResult could just make a new ClientFax record, load the variable into a big  unbound text editor field or multiline field, then PrintAForm that current record, then delete the contents of the field, and loop to the next client, etc.  ??? 


Or maybe I just need to 'man up' and tackling PrintString arcanity.  But that kind of tedious pixel placement and testing usually makes my neck lock up 

Fax: 555-2286

Need Soon Report from WordCom, Inc
Hi,
1007N / Customer ENGINEERING, DEAN'S OFFICE

WordCom's wise, all-seeing White Owl Software suggests that
you are due to order the following products - please contact us
via fax 918-our-fax#, phone 918-our-phon#, or email ouremail@ourweb.com.
We appreciate you !!!


Reorder Date for 4 CTN of ItemNum #1-5511G / Paper, WC, 8511-20, 20# 92-BRITE WHITE COPIER/LASER PAPER #851001HS - G packaging, High Speed
should be 2013/04/02

MergeFilePrint ( ) will print the records using loop. Would you be printing to Fax printer? Or do you have a fax server?  You could use Commandline fax program to pass on the fax# and name. It will be a little slower as compared to Printstring as it has to open up the MS Word and close for each fax.


MergeFilePrint(vPath , "rtf", "", "", vExtFields, "", 0) //File will print without displaying

Hello Larry,

I'm not understaning the use of FormFieldValue() in this case. You are on that form, so can't you just use

NeedSoonBox = vNeedSoonFYI
vPrintForm = @PrintAForm(0, 0, 1, 0, 28,-1, -1, -1, -1, 1, 1)
Clear(NeedSoonBox) 

-Ray

Glad I could help.

-Ray