Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Need miracle!
Message
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Title:
Miscellaneous
Thread ID:
00701415
Message ID:
00701729
Views:
22
In all of our prgs, we have the printer codes stored to variables also. In most cases they are sent to the printer using ??? in dos and using 'set printer font' in vfp like the condensed example below:
* Get printer control codes for the selected printer, get printer fonts for
* this form, set the printer to name <>
DO PRINTSET    

#IF !'VISUAL' $ UPPER(VERSION())
    *Send any special codes required to the printer
    ??? opt
    *Send condensed print codes to the printer
    ??? av_condprt
#ELSE
    * Set printer font to the appropriate font for this form
    IF !EMPTY(sFontStd)
	SET PRINTER FONT &sFontStd
    ENDIF
#ENDIF

@  xrowreset, 0 SAY "Received from: " + mre_name
@  xrowreset,47 SAY ag_name
@  xrowreset, 0 SAY ""

#IF !'VISUAL' $ UPPER(VERSION())
    * Send standard font control codes to printer
    ?? av_stdprt
    EJECT
    * Send reset control codes to printer
    ??? resetopt
#ELSE
    * Set printer font to the default font for this printer
    IF !EMPTY(sFontStd)
	SET PRINTER FONT &dFontStd
    ENDIF
#ENDIF

* Set device back to screen, etc
DO PRNTRSET	
I guess what I am concerned about is how to globally manage this since our reports are in hundreds of prgs (literally). Most of the same code is run in the FPD26 version as well as VFP7 using the '# !VISUAL' conditions above. I guess I will play around with one report first as a test. Some of our reports are done entirely using '? and ??, etc' also. That is why we were slowly working towards converting all to frx's but that will take months to accomplish. Thanks for the ideas and examples!

Tracy

>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).
>
>
>
>** 1
>if printcmd = 'N'
>   set device to file c:\prtemp.htm
>else
>   set device to print
>endif
>
>** 2
>** old
>*!*	*** SET CPI FOR LASER PRINTER
>*!*	mp10 = 'chr(27)+"(s0p10H"'
>*!*	mp12 = 'chr(27)+"(s0p12H"'
>*!*	mp16 = 'chr(27)+"(s0p16.66H"'
>
>** new
>*** SET CPI FOR LASER PRINTER
>mp10 = ['<font size="3">']
>mp12 = ['<font size="2">']
>mp16 = ['<font size="1">']
>
>** 3
>   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
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Previous
Reply
Map
View

Click here to load this message in the networking platform