cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Andre
‎09-01-2015
  • 273 Posts
  • 1 Likes Given
  • 0 Solutions
  • 41 Likes Received

Re: reset result for print

by Obsidian | Level 7 in Graphics Programming
‎08-09-2012 10:21 AM
‎08-09-2012 10:21 AM
gsub'ods html close;ods preferences;ods html path="$sysfunc(pathname(WORK))";' is just at the limit of what a ctrl + G  by example can accept BE AWARE  that i tried without blank   gsub'  and no blank if it is  not necessary then one action and you are  in a new  refreshed context BUT ALWAYS writing  in your work  (and not in your current directory) a second or third sashtmln.htm  file May i conclude with a wish for the ballot  that the length of the key buffer must be longer Andre ... View more

Re: reset result for print

by Obsidian | Level 7 in Graphics Programming
‎08-08-2012 06:06 PM
‎08-08-2012 06:06 PM
By default you are under html destination and probably reading your output in the result viewer so you see a big html file growing so until you don't submit the following, you wil  remain in that situation ods html close; ods preferences; and eventually reopen a new html file with ods html; with then a new html file in your current directory but if you type ods html path="%sysfunc(pathname (work) ) "; the second html file will well go inside the work directory the advantage is that when you are trying graphics a lot all the png files are scratched at the end of the sas session I too at the beginning was disturb by the new ods destination but if you are in a test phase it is usefull. Please read more from contributions on this topic from the global forum 2012 a long illustrated text of Cynthia or from the sas help  as you were advertised at the start of 9.3  that the rules were changing. paper 250-2012 "Where's the listing Windows: using the new results viewer in sas 9.3" support.sas.com/resources/papers/proceedings12/250-2012.pdf Andre ... View more

Re: PROC TABULATE with ODS TAGSET

by Obsidian | Level 7 in ODS and Base Reporting
‎07-30-2012 07:51 AM
‎07-30-2012 07:51 AM
Krudel Your code (without style as this could be another problem)  is working well under sas 9.3.0 now it is true that the opening of the xml file in the resultsviewer encounter an advertisement that ask you to allow this opening. but if you go in the results windows and you double click  after on the table1 excel icon you can see that the xml file is correct and well readed by excel Don't forget to save this file in a real .xls file or .xlsx/xlsb file depending of your version of Excel. André see perhaps too http://www.sascommunity.org/wiki/Tips:Automatically_opening_Excel_workbooks_created_by_the_ExcelXP_tags or http://support.sas.com/kb/38/266.html ... View more

Re: NO style anymore with simple ODS

by Obsidian | Level 7 in ODS and Base Reporting
‎07-25-2012 05:56 AM
‎07-25-2012 05:56 AM
Jaheuk, Please apply those two instructions in order to see what is happening under your non-windows environment  ( i guess from rs=none). ods path show; ods path reset; Andre ... View more

Re: Create a list of Excel files on Linux and then PROC IMPORT them.

by Obsidian | Level 7 in SAS Programming
‎07-20-2012 03:39 AM
‎07-20-2012 03:39 AM
Hi Peter, Yes this code is working under 9.2.3 filename s "~wi/tourism.xls"; proc export data=sashelp.tourism outfile=s replace  dbms=xls;             newfile=yes; version=2003 ;run; proc import datafile="~wi/tourisme.xls" out=sp4test dbms=xls;run; proc import datafile="~wi/testpoursas.xls" out=sp4test3 dbms=xls; sheet='Feuil2'n;        run; proc import datafile="~wi/Fichecp.xls" out=sp4test4  dbms=xls; sheet='Feuil1'n;        run; Andre ... View more

Re: tagsets.tableeditor - options to export to Excel

by Obsidian | Level 7 in ODS and Base Reporting
‎07-12-2012 07:17 AM
‎07-12-2012 07:17 AM
Pinklemon i tried under excel 2010 and sas 9.3 with the corresponding tagsets for 9.3 I encounter many difficulties 1 the tagsets for 9.3 must be downloaded from sas page 2 i was working with firefox and not with IE  as default browser  and with the result viewer inside sas 9.3   and  IE addon of firefox was not accepting the script of the activex control... of the by sas builded page so i correct  to                   IE as default for sas  to view ods results and no more result viewer! and  this code was working  with the advice of allowing the activex script under IE and excel was finally created i don't think direct export to excel is possible  (as tableeditor was designed for html) except an export from the  excelxp tagsets  by the mean of xml followed by an opening action of excel on this xml file. Andre NOTE in the code :  excel_save_file="D:\\temp\\exporttoexcel.xls" double slash everywhere for IE ods html close; ods path sasuser.templat(update) sashelp.tmplmst(read); ods tagsets.tableeditor file="D:\temp\exporttoexcel.html"           style=styles.mystyle           options(excel_zoom="90"                       excel_scale="90"                       excel_autofilter="yes"                       excel_frozen_headers="yes"                       excel_orientation="landscape"                       sheet_name="test"                       auto_format="color1"                       excel_save_file="D:\\temp\\exporttoexcel.xls"                       open_excel="yes"                     );     proc print data=sashelp.class noobs;  run;     proc print data=sashelp.shoes noobs;  run;     ods tagsets.tableeditor close; ... View more

Re: 9.3 name of the table template of proc print

by Obsidian | Level 7 in ODS and Base Reporting
‎06-29-2012 10:07 AM
‎06-29-2012 10:07 AM
So what's new for proc print behind "fully integrated" is quite only bounded with ods document! This was not clear from what's new in 9.3 pdf document! I had noticed already the by behavior comparing "ods traces"  between 9.2.3 and 9.3. Thank you Cynthia ... View more

9.3 name of the table template of proc print

by Obsidian | Level 7 in ODS and Base Reporting
‎06-29-2012 03:19 AM
‎06-29-2012 03:19 AM
The documentation says "The print procedure is now completely integrated with ODS." In comparison with proc freq  that was progressively integrated into ODS with specific output objects i am wondering in the case of the proc print output if and where is the specific table template that is behind the proc Or does the sentence means only that you may entirely act on the style template so that it relays the modifications  into the proc (without {style...} adds-on)   ? Andre Trace: Nom :          Print Libellé :      Table WORK.CLASS Nom données :  ProcPrintTable Chemin :       Print.ByGroup1.Print ------------- NOTE: The above message was for the following BY group:       Sex=F Sortie ajoutée : ------------- Nom :          Print Libellé :      Table WORK.CLASS Nom données :  ProcPrintTable Chemin :       Print.ByGroup2.Print ------------- NOTE: The above message was for the following BY group:       Sex=M ... View more

Re: ExcelXP Tagset Parsing Error

by Obsidian | Level 7 in ODS and Base Reporting
‎06-15-2012 03:50 AM
4 Likes
‎06-15-2012 03:50 AM
4 Likes
Tested under 9.3.0 with tagsets 127 i encounter no problem of opening with Excel 2010 8602  ods graphics off; 8603  ods tagsets.excelxp file = "d:\temp\ExcelXP.xls"; NOTE: Writing TAGSETS.EXCELXP Body file: d:\temp\ExcelXP.xls NOTE: This is the Excel XP tagset (Compatible with SAS 9.1.3 and above, v1.127, 09/26/2011). Add options(doc='help') to the ods statement for more information. 8604       proc reg data = sashelp.class; 8605       model Weight = Height Age; 8606       run; 8607       quit; NOTE: PROCEDURE REG used (Total process time):       real time           0.05 secondes       cpu time            0.06 secondes 8608  ods _all_ close; 8609  ods graphics on; ================================================= Under 9.2.3 with tagsets 127   no problem at all 8589  ods tagsets.excelxp file = "d:\temp\ExcelXP923.xls"; NOTE: Ecriture du corps du fichier TAGSETS.EXCELXP : d:\temp\ExcelXP923.xls NOTE: This is the Excel XP tagset (Compatible with SAS 9.1.3 and above, v1.127, 09/26/2011). Add options(doc='help') to the ods statement for more information. 8590       proc reg data = sashelp.class; 8591       model Weight = Height Age; 8592       run; 8593 quit; NOTE: Procédure REG a utilisé (Durée totale du traitement) : temps réel    1.03 secondes temps UC      0.26 secondes Conclusion   update your version of SAS? here is the tpl file ... View more

Re: autoexec insert or append in 9.3

by Obsidian | Level 7 in Administration and Deployment
‎06-12-2012 06:46 AM
‎06-12-2012 06:46 AM
Quentin inserting this in the sasv9.cfg -SET saslibn "d:\lib.sas" -APPEND AUTOEXEC saslibn provoke a fail at start of sas with the message Physical file saslibn does not exist  AND SAS  is searching  in the  -SASINITIALFOLDER "d:\My SAS Files\9.3"  ! ERROR: Le fichier physique n'existe pas, d:\My SAS Files\9.3\saslibn.  ERROR: The AUTOEXEC file d:\My SAS Files\9.3\saslibn cannot be accessed. The ERROR: SAS System will not be invoked. AUTOEXEC can be overridden with the ERROR: NOAUTOEXEC option. so i remark that SAS needs a real existing file name like lib.sas ! Andre ... View more

Re: autoexec insert or append in 9.3

by Obsidian | Level 7 in Administration and Deployment
‎06-12-2012 06:29 AM
‎06-12-2012 06:29 AM
Quentin, filename saslibn "d:\";   or filename saslibn "d:\lib.sas"; options append=(autoexec=saslibn); -are rejected in an ordinary program -are maked by  a green error 11 if inserted in an ordinary autoexec.sas                          the 11 apply to the words  insert= or append=  the only way that is working is in the sasv9.cfg  with a list of .sas files like in -INSERT AUTOEXEC ("d:\My SAS Files\9.3\autoexec.sas" "d:\lib.sas") so where did you see that a fileref was neccessary? on the two referenced pages? Andre ... View more

Re: autoexec insert or append in 9.3

by Obsidian | Level 7 in Administration and Deployment
‎06-12-2012 04:46 AM
‎06-12-2012 04:46 AM
Today trying again i have found some tricks If i set this in the sasv9.cfg file -INSERT AUTOEXEC ("d:\My SAS Files\9.3\autoexec.sas" "d:\lib.sas") without an icon with an explicit  -autoexec "d:\My SAS Files\9.3autoeexec.sas" the results is ok NOTE: AUTOEXEC processing beginning; file is ('d:\My SAS Files\9.3\autoexec.sas' 'd:\lib.sas'). NOTE: Libref A was successfully assigned as follows:       Engine:        V9       Physical Name: d:\notes\test NOTE: AUTOEXEC processing completed. If i put a options statement using append in the autoexec.sas file without any added line in the sasv9.cfg , the statement is rejected as invalid or  warning and the libref not created NOTE: AUTOEXEC processing beginning; file is d:\My SAS Files\9.3\autoexec.sas. NOTE: AUTOEXEC source line. 8      options append=(autoexec=("d:\lib.sas"));                     ------                11 NOTE: AUTOEXEC processing completed. this remain true with two files or with a insert= alternative. My conclusion is that you are only allowed to add lines to the sasv9.cfg the difference between -INSERT  or  -APPEND  autoexec ... are not clear  but you may have  a list of sas programs that are accepted all together as an entire autoexec.sas ! Andre ... View more

autoexec insert or append in 9.3

by Obsidian | Level 7 in Administration and Deployment
‎06-11-2012 11:08 AM
‎06-11-2012 11:08 AM
Hi, Reading sas documentation, i see that there are new system options  APPEND or INSERT tested upon the fmtsearch functionning already under 9.2.3 libname a "d:\notes\test"; proc format ; value rage low - 11 ='en avance' 12-14= 'jeune' 15-16 ='en retard' ; run; proc format library=a.fsex; value $sex "M"= "hommes" "F"="femmes"; options insert=(fmtsearch=a.fsex); proc freq data=sashelp.class; tables age * sex; format sex $sex. age rage.; run; proc options group=envfiles;run; there are no problems Group=ENVFILES APPEND=           Append at the end of the option value APPLETLOC=C:\Program Files\SASHome\SASGraphJavaApplets\9.3                    Location of Java applets AUTOEXEC=d:\My SAS Files\9.3\autoexec.sas                    Identifies AUTOEXEC files used during initialization FMTSEARCH=(A.FSEX WORK LIBRARY)                    List of catalogs to search for formats and informats INSERT=(fmtsearch=a.fsex)                    Insert at the beginning of an option value BUT when i tried to apply this to the AUTOEXEC   as mentionned as possible http://support.sas.com/documentation/cdl/en/hostwin/63047/HTML/default/n0jvezaeilaok4n1jqkv8t28b3o0.htm http://support.sas.com/documentation/cdl/en/lesysoptsref/64892/HTML/default/p1q9ay0ai0h2ein1n68qxomnm3q7.htm   i am misslucking the functionning  following those changes i have created a sas program  " lib.sas" at root of D:\  with the only line                         libname a "d:\notes\test"; in order to   "ADD" if i may say a second kind of autoexec.sas  to the existing one with the goal adding a sas pgm with one or many libnames 'at start of sas'! so i have written this last line in my sas9.cfg (following the description of the documentation presenting only a fmtsearch= sample but pretending autoexec is allowed) -APPEND AUTOEXEC  "d:\lib.sas" and at restart the original program  (with a  neutralized libname line of course) shows an error as  libref a is not existing  ===> symtom that the second APPENDing operation was not successfull. Has somebody of you already tested this kind of new starting mode of sas 9.3.0 this remain true with -SET  SASLIBN  "d:\lib.sas" -APPEND AUTOEXEC SASLIBN NOTE: L'initialisation de SAS used:       real time           1.29 secondes       cpu time            0.95 secondes NOTE: AUTOEXEC processing beginning; file is d:\My SAS Files\9.3\autoexec.sas. NOTE: AUTOEXEC processing completed. 1 2 3    proc format ; 4    value rage low - 11 ='en avance' 12-14= 'jeune' 15-16 ='en retard' ; NOTE: Format RAGE has been output. 5    run; NOTE: PROCEDURE FORMAT used (Total process time):       real time           0.03 secondes       cpu time            0.01 secondes 6    proc format library=a.fsex; ERROR: Nom A non attribué. TIA Andre i must add that if i suppress -autoexec "d:\My SAS Files\9.3\autoexec.sas" (and addd -verbose) the resuts are -for my try with saslibn   a severe error with the saslibn substitution but i have perhaps made an error -for my try  with  -insert autoexec "d:\lib.sas"     the substitution of autoexec.sas by  lib.sas ... View more

Re: Reading Euro symbol from external file

by Obsidian | Level 7 in SAS Data Science
‎06-08-2012 06:13 AM
‎06-08-2012 06:13 AM
There is a new book at SAS "Sas encoding  understanding the details "  by Manfred Kiefer   175 p where the euro symbol is well mentionned as Latin9  ! http://support.sas.com/publishing/authors/kiefer.html options locale=fr_FR; this options seems now from 9.3  accepted by  SAS Foundation so if anybody  in the USA  can test my answer on an american version of SAS it may be now more easier to treat those kind of difficulties  without the reserve i have presented in matter of encoding= and after return to options local=English_UnitedStates; sorry but after reading more into the nls manual the change of locale has only effect upon dflang=    datestyle= and papersize= sorry again you have to start sas with another encoding or make use of the encoding=   options in proc import, infile and so on Andre ... View more

Re: ODS title statement with background colors and url linkage for eac...

by Obsidian | Level 7 in ODS and Base Reporting
‎06-08-2012 04:19 AM
‎06-08-2012 04:19 AM
Hi Lawrence, Studying the outputs, i see finally that it works under 9.3.0 and 9.2.3 BUT i recognize that with html destination  the buttons are refering to the correct hyperlinks with pdf indeed yahoo is present twice!   and this is an error with rtf  the hyperlinks are correct another way to obtain your goal could be . title2 link='http://www.ined.fr' "B"; So once again ods adaptations are not universal! Sorry and ask for help to the sas support. and transmit them the error we have discovered! After, please report here about the error too. Andre ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎09-01-2015 07:11 AM
Likes given to
View All
Likes from
Quick links