I'm not sure what you mean by the // port.......perhaps that only
applies to Windows NT/2000 networks? I would bet it is safer to print
to a file then copy the file to the port. If nothing else, if the
report does not look right, you can go back and edit the file, and send
it again...that's how I figured things out.
I left all the variable fields long enough to cover the length of the
printer control codes, AND (I forgot to mention this part....) under
properties for the fields, TURN AUTO EXPAND OFF!! If you don't the first
printer control code seems to over write the following codes.
The height of all of the regions such as RH and RF all have to be at
least some certain height, about 1/4" or they don't send the printer
control codes at all!! Also, when you are creating your printer control
code variables, it appears they all get assigned to the Detail
section....NOT GOOD! You have to click on the Variables option at the
top of the screen and then click on Change Section, and reassign each
variable to the correct section and THEN place them in the correct
Section. If they are already in the correct section, but they are
assigned wrong, delete the variable and start over...don't just try to
change the section, it won't work! In fact, lots of variables after my
conversion were assigned incorrectly, and it made it impossible to move
the green section lines to make sections bigger or smaller.
I hope this helps!
Mike Sinclair
"J.M. GRATIAS" wrote:
>
> Mike Sinclair :
>
> >>
> Ok.....I finally figured out how to do this. For those of you who need
> to use printer control codes from within Rbase for Windows, here is what
> I found that works.
> 1) You have to have a "Generic/Text only" printer set up as your windows
> printer.....anything else eats the printer control codes.
> <<
>
> When the printer is connected to the // port, do you print directly to it
> thru Windows printer's manager ?
>
> >>
> 3) Create the variables in the report using the CHAR function, but put
> parentheses around the whole thing.....ie
> vRESET = ( (CHAR(27)) + (Char(67)) ) .....notice the extra ()
> <<
>
> Is the variable's width important ?
> (I.E. if the escape command is 20 char long, must it be wider than the one
> for 2 char ?
>
> >>
> 4) Areas such as the REPORT FOOTER have to be at least some certain
> size, about 1/4 inch or the variables/printer control codes you put in
> there won't get used.
> <<
>
> I suppose the same remark apply to RH (if you need to send commands to
> initialise the printer) ....
>
> >>
> I hope this helps somebody.
> <<
>
> Oh yes, it does ....
> I'll try that as soon as I can. A great thank you for your precious
> explanations ...
>
> J.M. GRATIAS, Logimatique, France
