Mike,
  On the odd size forms, did you try custom label instead of report?

----- Original Message ----- 
From: "Michael Sinclair" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, January 14, 2008 6:15 PM
Subject: [RBASE-L] - Enhancement request for Printer Control Codes in Rbase 7.6


> Hi all!
>
> I am still working on getting Printer Control Codes to work. I have confirmed 
> that they are not supported in Ver 7.6. I have submitted a request for an 
> enhancement to the knock your socks off team!
>
> The reason for the request is because of the need to print on tractor feed 
> forms. There are times when the end user is required to fill out original 
> forms where laser forms are not available.
> An example would be a doctor's office where the doctor wants to have Rbase 
> print perscriptions. The perscriptions are usually not 8.5" x 11", instead 
> they are more like 4" wide x 5" in height.
> Finding a laser printer that would handle such an odd size piece of paper one 
> at a time would be difficult. Printing the perscriptions on 8.5" x 11" paper 
> would be awkward and possibly subject to
> abuse (duplication via a copy machine).
>
> Also, the original tractor feed forms frequently require filling in data at 
> the top edge of the form, which is above the area where the print head sits 
> at rest. In order to avoid wasting the first form, the user would need back 
> up the form to line up the top of the form with the top of the print head 
> which would be pretty inconvenient. The other choice would be to roll up the 
> forms on the printer and waste the the first form by leaving it blank (wastes 
> paper and is not good for the environment or trees!).
>
> Likewise, some tractor feed forms are not designed very well. They have 
> fields that are not horizontally lined up. In those cases, you need to be 
> able to move the form up and down by fractions of a line to get the data to 
> print in exactly the correct location. Failure to do so would not only look 
> sloppy, but it might cause the recipient of a from using an OCR program to 
> fail to get the data properly.
>
> I am actively trying some of the suggestions that came from this awesome 
> support group. I really appreciate your help. I will report back if I come up 
> with something that works.
>
> Mike
>
>>
>
>
> 


Reply via email to