Hi Emmitt, Is there some reason that I would have to change the printer control codes when moving from version 6.5 to version 7.5? This report worked great in version 6.5. All I did was have version 7.5 convert the report. I checked the new report in version 7.5 and the variables are all the same as those in 6.5. However, what is not the same is that the variables are called Variable Lables (Label Variables?) in Ver 7.5...in version 6.5 they were just "Variables." I tried using the other types of variables such as rich text and memo, no change. I tried changing the variable type from text to varchar, still no change. It is acting like Ver 7.5 does not send the pure [ESC]code to the printer.
Mike -------------- Original message from "Emmitt Dove" <[EMAIL PROTECTED]>: -------------- Mike, You have to make certain that you put together the exact string the printer wants to see. So you need to use (CHAR(27)) for [Esc]; some codes may require (CHAR(1)) or (CHAR(0)); dont confuse those with 1 and 0. Be very meticulous about the presence or absence of spaces in the string. Id suggest first working out the string in a plain text file and getting it to make the printer move up, then use that result to build your variable. Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022 From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, January 12, 2008 10:53 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Printer Control Codes in Rbase 76 I might be getting closer...this is what the output file looks like... @ 0 C" j½ NAME: John Smith AGE: 104.109 AMOXIL 500 MG 1 PO TID X 10 DAYS QUANT: {30} REFILLS: {NONE} VOID AFTER 01/19/2008 ______________________________ MS DEA#: CALL TO VERIFY 8000. DATE: 01/12/2008 j6 The top 4 charater sets and the very bottom characters are supposed to be my printer control codes. But instead of controling the printer, the printer just prints those symbols! How do I get the values sent to the printer without having them print....like they did in Rbase 6.5? Mike -------------- Original message from "Emmitt Dove" <[EMAIL PROTECTED]>: -------------- Id use text. Something like: Variable name: vMoveUp Type: Text Formula: (CHAR(27)+[the escape string needed]) Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022 From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, January 12, 2008 10:32 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Printer Control Codes in Rbase 76 Hi Emmitt! I will give that a try...does it matter which kind of variable I use in the report to represent the printer control codes? Thanks! Mike -------------- Original message from "Emmitt Dove" <[EMAIL PROTECTED]>: -------------- > Mike, > > What I would do is create a report that is set up to be text-only (File | > Print to Text File Setup | File Type - Fixed Length > > Then, create your report as appropriate, embedding the printer control codes > in variables and placing appropriately on the report. Now, print your > report to the text file, and ZIP CMD /C COPY filename.txt PRN. > > It may not be the *only* way, but it should work. If it seems to be too > much of a pain to go this route, then revert to a PAGEMODE report ... > > Emmitt Dove > Manager, DairyPak Business Systems > Blue Ridge Paper Products, Inc. > [EMAIL PROTECTED] > [EMAIL PROTECTED] > (203) 643-8022 > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michael > Sinclair > Sent: Saturday, January 12, 2008 6:27 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Printer Control Codes in Rbase 76 > > The missing link is that there does not appear to be any way to move the > paper up and down > unless there is a way to send a command to the printer. Do you think it > would be possible to > send the report to a file and then copy the file to the printer in order > to get the printer to move the > paper backwards? > Mike > > MikeB wrote: > > Here is all I can find from Sami, but it refers to Pre 7.x, which > shouldn't be > > an issue as long as you can approximate it in 7.x. Just give it a Shot > and > > test to blank paper (don't waste preprinted) I just print to blanks and > hold > > up to light till I get close. > &g t; > > 1. You can design a "Custom Report" to print any kind of custom checks. > > > > Tips: > > . Use ONLY PH (Page Header) Section of Report (Key Point) > > . Remove all other sections, i.e, RH, D, RF, etc. > > . Under Report Layout, > > . Lines Per Page: 74 > > . Page Footer Line Number: 0 > > . CHECK [Remove Initial Carriage Return] > > . UN-CHECK [Manual Break Reset] > > . CHECK [Clear Variables after Printing] > > . UN-CHECK [Form Feed - Before Printing Report] > > . UN-CHECK [Form Feed - Before Report Header] > > . UN-CHECK [Form Feed - After Report Header] > > . UN-CHECK [Form Feed - After Report Footer] > > . SET Print Orientation to Portrait > > . SET Left Margin to 0.75 > > . SET Right Margin to 8.00 > > > > ; 2. You can also use Custom LABEL feature of R:BASE for Windows > > > > You don't need that. R:BASE FOR WINDOWS 6.1/6.1A DOES IT ALL! > > > > Under "Report Settings", you can pre-define the "Print Orientation" to > > Landscape. > > > > > > ----- Original Message ----- > > From: "Michael Sinclair" > > To: "RBASE-L Mailing List" > > Sent: Saturday, January 12, 2008 5:46 PM > > Subject: [RBASE-L] - Re: Printer Control Codes in Rbase 76 > > > > > > > >> Hi Mike, > >> There are times when you have to print on an original preprinted forms > >> (perscriptions for controlled substance, FAA pilot forms, etc). > >> If that is the case, can Rbase for Windows 7.6 reports utilize printer > >> control codes or is there some workaround? > >> Mike > >> > >> > >> MikeB wrote: > >> > ; >>> ----- Original Message ----- > >>> From: "Michael Sinclair" > >>> To: "RBASE-L Mailing List" > >>> Sent: Saturday, January 12, 2008 4:17 PM > >>> Subject: [RBASE-L] - Printer Control Codes in Rbase 76 > >>> > >>> > >>> > >>> > >>>> Hi all! > >>>> I am trying to convert a report in Rbase for Win 6.5 to ver 7.6. The > report > >>>> has to be typed on a roll of preprinted > >>>> perforated forms. The forms are 4.25" tall, 5.5 " wide (plus the > tractor > >>>> feed strips). They are being printed on a > >>>> dot matrix Panasonic KXP 1150 printer that has those wheels with spi kes > >>>> > >>>> > >>> I still have a good (although not used for at least 6 years) one lay ing > on a > >>> shelf that I gave up on and just went to printing multiple copies > through a > >>> laser instead of multipart dot matrix. It is just a pain. > >>> > >>> I think Sami had some ideas on this from about 5 or 6 years back too. > It > >>> was Check printing, IIRC. > >>> > >>> > >>> > >>> > >>>> on both sides of the roll of forms that grab > >>>> the form and shoves it through the printer. Further more, when the > printer > >>>> is at rest, the top of the perforation of the next > >>>> form to get printed on is at the perfect level so that the user can > tear > >> >> off the last form right on the perforation line. > >>>> > >>>> Now if you are with me so far, here is the tricky part. I have to start > > >>>> printing ABOVE where the print head sits when the form > >>>> and printer are at rest. In Rbase for DOS and Rbase for Windows, I used > > >>>> printer control codes embedded in the report to make > >>>> the printer roll the paper backwards just the right amount to start > >>>> printing, and then at the end, advance the paper just enough so > >>>> that the perforation would be at the right place to facilitate tearing > off > >>>> the printed form. > >>>> > >>>> I let Rbase for Windows 7.6 convert the form, and now it prints funny > >>>> little symbols on the report rather than moving the paper > >>>> up and down. > >>>> > >>>> How do I put printer control codes in Rbase for 7.6 reports? Or is > there > >>>> some other cooler way to get the same thing done? > >>>> Thanks for reading my long winded wordy question!!! > >>>> > >>>> Mike > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> > >> > >> > > > > > > > > > > > >
