Hi Tracy,
>>Another way to go is to display them as HTML documents in an embedded
>>IEBrowser control in a form. Luckily for me the reports are all written
OK. I got the proof of concept working.
Luckily (for me) the former coder created a secret option to print to a text file -which I renamed to prtemp.htm (** 1).
And he had already stored the different CPI setting commands to memory variables, so I just set them to HTML control tags (**2).
So when I choose to run the report but not send it to print, the prtemp.htm text file (containing my report) gets wrapped in some obligatory HTML code and saved to a file for viewing (** 3).
if printcmd = 'N'
set device to file c:\prtemp.htm
else
set device to print
endif
mp10 = ['<font size="3">']
mp12 = ['<font size="2">']
mp16 = ['<font size="1">']
set device to screen
m.duh=FILETOSTR('c:\prtemp.htm')
m.duh='<html><body>'+CHR(13)+m.duh+CHR(13)+'</body></html>'
=STRTOFILE(m.duh,'c:\reportview.htm')I'm still going to investigate what Peter was talking about but so far this little kludge seems to work like a charm!
Hugh
Microsoft hears loudest what the VFP community says about Visual FoxPro by looking at the bottom line!
Support the product. Buy the latest version!
Hugh Winters @ WorldData 408-512-1131
