>>>
>>>>
>>>>Thanks Matt, I will give that a try. Any way to tell VFP to print the mail merged document automatically after I create the free table? My client has asked me to print all these cover letters automatically while I am printing the reports (immedicately beforehand so they come out in the correct order).
>>>>
>>>>GeneS
>>>
>>>I think there's OLE automation available for Word, but never having used it, I don't have the foggiest idea how to. Another idea that may or may not work...can you call an executable from within a macro in Word? Maybe the mail merge can be done with a macro that calls your export app first?
>>>
>>>HTH/HTW
>>>
>>>Matt
>>If MS would give us the source to PRINT PREVIEW, we would
>>not have these problems.
>
>print preview wouldn't affect mail merges. most products have problems reading anything in the dbc container. anything native to fox (foxfire) or that can use odbc (crystal reports) can get the data into a mail merge file which can then be used by a word processing program.

I meant to respond to the below..
I got the wrong thread..
sorry for the confusion..

*********************

>>I am finding it hard to believe that our old Big Brother MS has provided us NO WAY to
tell if the Print button was pressed on the Print Preview toolbar. Maybe there's a way to
trap the event by going to the API? Any suggestions?
>
>I don't know how to capture pressing the print button, but how about using a global
memory variable? Like this:
>
>Create global memory variable glPrinted
>
>Create printon.prg:
>*PRINTON.PRG
>glPrinted = NOT glPrinted
>
>In the title band on entry event put:
> printon()
>
>In your code to preview and print:
>
>glprinted = .T.
>report form preview
>IF NOT glprinted
> IF (your message program) = "Yes"
> report form to print
> ENDIF
>ENDIF
>
>I am assuming that you don't want to show a message asking if the user wants to print
a report when they've already printed it from the preview toolbar.
>
>HTH,
>Valerie