Re: Bizarre Printing Problem
From: Jeroen van Kalken (I_at_dont.like.spam)
Date: 10/19/04
- Next message: Ranil Rupasinghe: "Distinguish between report controls in different report bands"
- Previous message: SlackJaw: "Bizarre Printing Problem"
- In reply to: SlackJaw: "Bizarre Printing Problem"
- Next in thread: Lisa Slater Nicholls: "Re: Bizarre Printing Problem"
- Reply: Lisa Slater Nicholls: "Re: Bizarre Printing Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 19 Oct 2004 10:41:44 +0200
On Mon, 18 Oct 2004 20:21:01 -0700, "SlackJaw"
<SlackJaw@discussions.microsoft.com> wrote:
Its not a bug, its a feature.
the { allows you to insert unprintable characters without the use of
CHR(). Just include something like {27} in your file and it will send
an escape code.
This also means you have to preprocess the { char to {123} using
something like strtran(lcText,'{','{123}')
(Strangely it is not documented anymore in VFP8, it was in FPD/W 26)
>Hello,
>
>Really strange problem. I've been trying to send preformatted files to
>WIndows printers with a VFP8 application. I use the filetostr to load the
>file to a variable and I use the handy ??? command to send it to the printer
>bypassing the printer driver. Works great unless...
>
>The value of 123 (which is the '{' character) is stored in any of the bytes
>of the file. No kidding and no idea. Generates a syntax error.
>
>The error doesn't occur if the '}' is sent with it. Very strange and
>definitely a bug. Now I'm investiagting API calls. Any other ideas?
>
>Thanks,
>
>KV
- Next message: Ranil Rupasinghe: "Distinguish between report controls in different report bands"
- Previous message: SlackJaw: "Bizarre Printing Problem"
- In reply to: SlackJaw: "Bizarre Printing Problem"
- Next in thread: Lisa Slater Nicholls: "Re: Bizarre Printing Problem"
- Reply: Lisa Slater Nicholls: "Re: Bizarre Printing Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
