Razzak I went to download the unreleased update you mentioned. I should have recognized the 'Blues Clues' inference. It certainly gave me the blues and I didn't catch the clues. I understand now that my problem will be solved 3/15/09. The only question I have now is, How is it that you are fixing a problem that I am having before I realize that I am having it?
I humbly remain the student Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Saturday, March 14, 2009 10:56 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: printing a report to a file Mike, I guess you missed the fine and very clearly stated details in my reply, that included the specific references to R:BASE 7.6 Update 6 (Build: 7.6.6.30315) and R:BASE Turbo V-8 Update 20 (8.0.20.30315). Are you using that specific version/update? I was told once that reading between the lines is essential so you don't miss anything important. If you still haven't figured it out yet, you may have to login to get the exact version and updates at www.rupdates.com on 03/15/2009 (either 7:56am morning or 8:00pm evening). You will have to try at either time exactly <g>. Enjoy the weekend! Very Best R:egards, Razzak. At 10:21 AM 3/14/2009, mike epstein sony viao office wrote: >Good Morning, > >Razzak, after countless tries of all the combinations of options to print a >report to an ETXT file. I went to the sat application RRBYW15 used the code >(copied and pasted from your email) > > >PRINT CustomFormLetter WHERE CustID = 128 + > OPTION ETXT + > |FILENAME CustomFormLetter.TXT + > |INCLUDE_RICHTEXT ON + > |RICHTEXT_ENCODING_TYPE PLAINTEXT + > |SHOW_CANCEL_DIALOG OFF + > |OPEN ON > >It gave me the same response , the txt file named customformletter.txt when >opened by notepad did not display the rtf object in the report. I know that >you said that it did and I'm sure it did . What could I be doing > >This is the code I have used in my database with the same results as above >PRINT cust_CMRKLTR3v2 WHERE jidcode =101 + > OPTION ETXT + > |FILENAME vmemo.TXT+ > |INCLUDE_RICHTEXT ON+ > |RICHTEXT_ENCODING_TYPE PLAINTEXT+ > |SHOW_CANCEL_DIALOG OFF+ > |OPEN ON > >Needing some greatly appreciated help here. > >Mike > >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak >Memon >Sent: Friday, March 13, 2009 10:31 AM >To: RBASE-L Mailing List >Subject: [RBASE-L] - Re: printing a report to a file > >At 08:30 AM 3/13/2009, Mike Epstein wrote: > > >Razzak > > > >PRINT BID2FBTXT WHERE BIDNUM = 186 OPTION ETXT |SHOW_CANCEL_DIALOG > >ON|FILENAME t.txt|OPEN ON|INCLUDE_RICHTEXT ON|RICHTEXT_ENCODING_TYPE > >PLAINTEXT > > > >The line above gives me the same response 'the rich text part of the > >report does not print' Other fields in the report Do print but the > >rtf field does not. > >Very interesting, Mike! > >Here's what I did to test the similar scenario on my end: > >01. Started R:BASE 7.6 Update 6 (Build: 7.6.6.30315) >02. CONNECted to RRBYW15 (Running R:BASE Your Way! Part 15) >03. Used the following command to PRINT the report with embedded > Rich Text control as Report Emulation Text File (ETXT). > > PRINT CustomFormLetter WHERE CustID = 128 + > OPTION ETXT + > |FILENAME CustomFormLetter.TXT + > |INCLUDE_RICHTEXT ON + > |RICHTEXT_ENCODING_TYPE PLAINTEXT + > |SHOW_CANCEL_DIALOG OFF + > |OPEN ON > >The resulting text file (CustomFormLetter.TXT) looks A-OK, >including the RTF contents as plain text. > >Using the R:BASE Turbo V-8 Update 20 (8.0.20.30315) also reveals >the same A-OK results. > >What version and update are you using? > >Hope that gives you some blues clues .... > >Very Best R:egards, > >Razzak.
