About BlackTea

BlackTea · ‎11-11-2013

Hi Jagadish, Thanks! But with just=d I got same results regardless of whether I use values with decimal point or with decimal comma: it's not aligned. I wonder why just=d isn't working even with the comma. Daniela

BlackTea · ‎11-11-2013

Hi there, I tried to get character data decimal aligned in rtf output. I tried to do this here: 24045 - In ODS RTF, can I modify the alignment from always being centered on the decimal? data test; x='1.9'; output; x='1.91'; output; x='1.'; output; x='12.'; output; run; ods rtf file='c:\file.rtf'; proc report data=test nowindows split="|" headline headskip; columns x; define x / display"Dose 1|(n=457)" width=15 style(column)=[protectspecialchars=off pretext="\tqdec\tx500 "]; run; ods rtf close; In the first place it didn't work. Then I finally got the idea that it does not work because of the german installation of my MS Word. So, with the values comma-separated it worked fine! But, I have to produce the output with decimal points. Therefore, my question is: how can I tell Word that it shall use the decimal point and not the comma for the decimal alignment? Is there a possibility? Can I do this within the pretext-option or do I have to modify my rtf template or...? Thanks very much in advance, Daniela

BlackTea · ‎07-18-2013

I tried to use ods csv because all the other things didn't work, so I also tried ods csv and thought that it would be the best way to modify this tagset to get my result. But I was wrong I know that proc export doesn't really insert an empty blank data line. But SAS on a Windows system writes a line feed and a carriage return (hex = 0D 0A) at the end of each line. Which is perfectly correct. So it happens that at the end of the file there is an empty line displayed because of the carriage return, and I guess that the system to which the file is being uploaded is maybe not a Windows system, thus it misinterprets this last "empty" line as an empty data line. But, I managed to create this file without this last LF and CR by combining your proposal and this one here: https://communities.sas.com/thread/14211?start=0&tstart=0 data _null_; file "Z:\temp\test.csv" recfm=n; length row $1000; set test ( keep = var1 var2 var3 var4 ); row = catx( ",", var1, var2, var3, var4 ); if _n_ = 1 then put "var1" "," "var2" "," "var3" "," "var4" "0D0A"x; if _n_ > 1 then put "0D0A"x; put row; run; Thanky very much!

BlackTea · ‎07-10-2013

Hi, I use proc export to write a csv file which will be uploaded into another system. The problem is that this csv file gets a blank line at the end, this troubles this other system. I tried to write this file with ods csv tagset, but then even two blank lines are inserted. I modified the csv tagset in the event table and accomplished to avoid one of the blank lines. I found the place from where the second line is coming, but I don't know how to modify that this blank line will not be written. I've also tried with file and put statement in a data step, but one blank line is added as well. Here is my proc export: proc export data = test outfile = "Z:\temp\\test.csv" dbms = dlm replace; delimiter = ","; run; Here is my export with the modified ods csv tagset. The remaining blank line is written during the row event by put NL; which is appended to each written row to start a new line for the next row, which I don't need for the last row. proc template; define tagset tagsets.csvnoq / store=sasuser.templat; parent=tagsets.csv; define event quotes; end; define event table; end; define event row; finish: do /if $cell_count; close; eval $cell_count 0; else /if $$row; put $$row; unset $$row; done; put NL; end; end; run; ods tagsets.csvnoq file = "Z:\temp\test.csv"; data test; do var1 = 1 to 100; var2 = var1; output; end; run; proc print noobs data=test; var var1 var2; run; ods tagsets.csvnoq close; I hope someone has an idea what else I can try or how to get rid of the blank line in the last row via the csv tagset. Many thanks!

BlackTea · ‎01-03-2013

Benn must add the format statement to see the internal date value as he wants. 2039 and 2070 and so on in the number since 01JAN1960. Readin the SAS Online doc in the chapter About SAS Date, Time, and Datetime Values

BlackTea · ‎12-12-2012

But the continued tag at the end of a table which has page breaks is now gone

BlackTea · ‎12-10-2012

Hi Cynthia, many thanks four your hint! In the meantime the SAS Support got me this technical note: 45138 - Creating an RTF file using a modified version of TAGSETS.RTF generates an RTF file without any style information which lists the bug due to which I cannot create my own tagset in the common way. If I go for the described workaround it works fine and I am able to modify the tagset for the title and footnote inclusion. But with the rtf_sample tagset it is not necessary any more! I don't know why this tagset thing is so unpopular. It really cuts down the working time for the creation of listings for a whole database! Daniela

BlackTea · ‎11-30-2012

Hi, I have the same "problem" ( see https://communities.sas.com/message/144593#144593 ) and thought that I could solve it like described here http://www.phuse.eu/download.aspx?type=cms&docID=4197 But I cannot modify my tagset due to a SAS bug (I have SAS 9.3 M0), perhaps you can do it. I think that one must modify the pagebreak event where the rtf control code for header and footer is defined. Maybe you can do it If yes, let me know...

BlackTea · ‎11-30-2012

Hi, just for information: I made a SAS support entry and they could reproduce this behaviour, but do not know in which SAS maintenance release this bug will be solved...I don't understand though why this seems to work for the guy who wrote the presentation I have found (see my first post). I'm using SAS 9.3 M0

BlackTea · ‎11-14-2012

Hi there, I'm trying to modify the rtf tagset (I want to add a header and footer in the rtf document and seen here http://www.phuse.eu/download.aspx?type=cms&docID=4197 that this could be done somehow). So, my problem begins already by copying the tagset to a new tagset (WITHOUT ANY MODIFYING!). I tried it this way proc template; define tagset Tagsets.rtf_test; parent = tagsets.rtf; end; run; and I tried copying the rtf tagset code and modify the define statement like this: proc template; define tagset Tagsets.Rtf_test; ... tagset code ... end; run; After submitting the proc template, I can see the new tagset in my SASUSER.TEMPLAT storage in the Tagsets folder as rtf_test and all seemed to work well. But, when I call the new tagset like this: ods tagsets.rtf_test file="&gFilenameListings" uniform pagepanels=none style=ReportStyle.ReportStyle options(contents='yes' toc_data='yes' sect='off' toc_level='1'); %include "&gProgListings\Listing.sas"; ods tagsets.rtf_test close; The rtf which is created contains only the rtf control words and also not all data which should be in. The content of the rtf file is: {\fonttbl } {\colortbl; } {\*\bkmkstart IDX}{\*\bkmkend IDX} {\plain\f1\b0\i0\tc\v Listing 1 Demographics \tcf67 \tcl1 } \trowd\trkeep\trhdr\trql\trgaph0 {\row} \trowd\trkeep\trhdr\trql\trgaph0 {\row} \trowd\trkeep\trql\trgaph0 \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx3{294\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{ 8\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{13\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{ 12\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{Female \cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{170\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{ 80.0\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx8{28\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx11{not working\cell} \pard\plain\intbl\fs3\cf#000000\qr\b\tqdec\tx13{Skin type II \cell} {\row} \trowd\trkeep\trql\trgaph0 {\row} \sectd\linex0\endnhere \pard\par\par\plain{\field\fldedit{\*\fldinst { TOC \tcf67 \\h }}} \sect\sectd\linex0\endnhere\pgnrestart\pgnstarts1 {\header\pard\plain\qr\pvmrg\phmrg\posxr\posy0{ }} {\pard\par} {\*\bkmkstart IDX1}{\*\bkmkend IDX1} {\plain\f1\b0\i0\tc\v Listing 2 Visit Dates \tcf67 \tcl1 } \trowd\trkeep\trhdr\trql\trgaph0 {\row} \trowd\trkeep\trhdr\trql\trgaph0 {\row} \trowd\trkeep\trql\trgaph0 \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx3{294\cell} \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx11{16-APR-2010\cell} \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx11{28-MAY-2010\cell} \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx11{09-JUL-2010\cell} \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx11{09-OCT-2010\cell} \pard\plain\intbl\fs3\cf#000000\ql\b\tqdec\tx11{13-MAY-2011\cell} {\row} \trowd\trkeep\trql\trgaph0 {\row} } When I creatrt e my listing with tagsets.rtf and save the created rtf file as xml then I see that there is much more rtf control syntax in it. What am I doing wrong? I hope anybody could help me, because I don't understand this behaviour... Thanks in advance, Daniela

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: Decimal alignment in rtf output with german MS Word

Decimal alignment in rtf output with german MS Word

Re: Don't insert blank line in csv file

Don't insert blank line in csv file

Re: Converting Character into SAS dates

Re: Footnote placement in tagsets.rtf

Re: Creating my own rtf tagset does not work

Re: Footnote placement in tagsets.rtf

Re: Creating my own rtf tagset does not work

Creating my own rtf tagset does not work

Re: Footnote placement in tagsets.rtf

Re: Converting Character into SAS dates

Re: Don't insert blank line in csv file

Re: Decimal alignment in rtf output with german MS Word

Decimal alignment in rtf output with german MS Word

Re: Don't insert blank line in csv file

Don't insert blank line in csv file

Re: Converting Character into SAS dates

Re: Footnote placement in tagsets.rtf

Re: Creating my own rtf tagset does not work

Re: Footnote placement in tagsets.rtf

Re: Creating my own rtf tagset does not work

Creating my own rtf tagset does not work