12-22-2020
garfield
Fluorite | Level 6
Member since
08-22-2014
- 11 Posts
- 0 Likes Given
- 0 Solutions
- 3 Likes Received
-
Latest posts by garfield
Subject Views Posted 25007 05-23-2016 08:09 AM 25094 04-25-2016 10:58 AM 25125 04-20-2016 11:46 AM 3175 07-13-2015 09:28 AM 2532 07-13-2015 09:20 AM 3699 07-13-2015 09:16 AM 2532 07-13-2015 09:10 AM 3337 07-13-2015 08:40 AM 5093 08-22-2014 11:28 AM 5093 08-22-2014 10:05 AM -
Activity Feed for garfield
- Got a Like for Re: Lines Wrapping in ODS Excel - workaround. 07-24-2018 02:44 PM
- Got a Like for Re: Lines Wrapping in ODS Excel - workaround. 05-23-2017 05:17 AM
- Got a Like for Re: Lines Wrapping in ODS Excel - workaround. 09-06-2016 10:12 PM
- Posted Re: Lines Wrapping in ODS Excel - workaround on ODS and Base Reporting. 05-23-2016 08:09 AM
- Posted Re: Lines Wrapping in ODS Excel - workaround on ODS and Base Reporting. 04-25-2016 10:58 AM
- Posted Lines Wrapping in ODS Excel on ODS and Base Reporting. 04-20-2016 11:46 AM
- Tagged Lines Wrapping in ODS Excel on ODS and Base Reporting. 04-20-2016 11:46 AM
- Tagged Lines Wrapping in ODS Excel on ODS and Base Reporting. 04-20-2016 11:46 AM
- Posted Re: ODS Tagsets ExcelXP Creating Multiple Workbooks on Microsoft Integration with SAS. 07-13-2015 09:28 AM
- Posted Re: ODS Tagsets ExcelXP Creating Multiple Workbooks on Microsoft Integration with SAS. 07-13-2015 09:20 AM
- Posted Re: Using Task Scheduler to Run SAS on SAS Programming. 07-13-2015 09:16 AM
- Posted Re: ODS Tagsets ExcelXP Creating Multiple Workbooks on Microsoft Integration with SAS. 07-13-2015 09:10 AM
- Posted ODS Tagsets ExcelXP Creating Multiple Workbooks on Microsoft Integration with SAS. 07-13-2015 08:40 AM
- Posted Re: Error Using SAS/Access Can't Find Engine on SAS Data Management. 08-22-2014 11:28 AM
- Posted Re: Error Using SAS/Access Can't Find Engine on SAS Data Management. 08-22-2014 10:05 AM
- Posted Error Using SAS/Access Can't Find Engine on SAS Data Management. 08-22-2014 08:53 AM
-
My Liked Posts
Subject Likes Posted 3 05-23-2016 08:09 AM
05-23-2016
08:09 AM
3 Likes
Thanks for this! I was trying all of the other width options I could find and not having any luck.
FYI I had to combine this with the solution in the other thread I referenced for my data because some columns were still wrapping even though there was enough space.
Adding style(column)=data[width=1000% tagattr='wrap:no'] after the column definition in proc report fixed it.
Thanks again!
... View more
04-25-2016
10:58 AM
Thanks for the suggestion! However this won't work for what I actually need it for as I have a lot more text fields than this example, most of which require their spaces.
Any other ideas? I can't believe this isn't a bigger issue for people.
... View more
04-20-2016
11:46 AM
I'm having issues when using ODS Excel with text wrapping.
For some reason line breaks are being placed in some of my text fields and text wrap is being turned on causing much of the text to get cut off even when there is plenty of width for the text to fit.
I saw this post, here, however none of the work arounds listed there worked for me. Has anyone else figured out how to deal with this?
Below is an example, even with a super wide column width the text for player name still wraps.
ods Excel file="P:\test.xlsx"
OPTIONS( absolute_column_width='100')
;
PROC REPORT DATA = sashelp.baseball;
COLUMNS
Name
Team
nAtBat
nHits
nHome
nRuns
nRBI
nBB
YrMajor
CrAtBat
CrHits
CrHome
CrRuns
CrRbi
CrBB
League
Division
Position
nOuts
nAssts
nError
Salary
Div
logSalary
;
RUN;
ODS EXCEL CLOSE;
... View more
07-13-2015
09:28 AM
I found the solution by browsing "More Like This". I'm not sure how, but my global setting for the newfile option must have been changed at some point. I added this to my tagsets, newfile = none For reference here is the thread I found the solution in: https://communities.sas.com/message/119883#119883
... View more
07-13-2015
09:20 AM
I had different code initially but ended up just copying this from some SAS article to make sure it wasn't a mistake in my options. Even without that I still have the same issue.
... View more
07-13-2015
09:16 AM
I think your issue is that one of the lines in your program is too long for batch mode. There is a limit of 256 characters, see this page http://support.sas.com/kb/5/953.html.
... View more
07-13-2015
09:10 AM
Here is the jist of what I have: ods tagsets.ExcelXP path="&path.\Results\" (url=none) file="DATA &date_run..XLS" options(sheet_interval = "Table" sheet_label = " " sheet_name="Details" embedded_titles = "yes") style=Normal; proc report data=data nowd split='*' style(header) = {background=cx99ccff foreground=black font_size = 10pt FONT_WEIGHT = bold} style(column) = {font_size = 8pt} ; title1 "RESULTS FOR PAST TWO WEEKS"; . . . run; ods tagsets.Excelxp options(sheet_name="Unique IDs"); proc report data = uniqueids nowd style(header) = {background=cx99ccff foreground=black font_size = 10pt FONT_WEIGHT = bold} style(column) = {font_size = 8pt}; . . . run; ods tagsets.excelxp close;
... View more
07-13-2015
08:40 AM
I'm trying to use the ExcelXP tageset to create a single Excel workbook with multiple worksheets. However every proc report it comes to it creates a whole new workbook with 1 added to the end of the name I specify. For example I have the date in my workbook so it's Data 07-13-2015.xls. SAS then creates a workbook for each section the first one being Data 07-13-2015.xls then the next one being Data 07-13-2016.xls and so on for each section. I've tried adding a alpha character to the end such as Data 07-13-2015a.xls but that just results in Data 07-13-2015a.xls, Data 07-13-2015a1.xls, and so on. Any ideas what could be causing this? I did check and I'm using the latest version of the ExcelXP tagset: "NOTE: This is the Excel XP tagset (Compatible with SAS 9.1.3 and above, v1.130, 08/02/2013)"
... View more
08-22-2014
11:28 AM
It's a Windows machine. I believe all the syntax is correct because I use the same syntax on my machine to connect to those databases. I can also confirm they are able to connect to those databases on their computer through other programs besides SAS. The issue seems to be that the products aren't properly installed. My question is, is there someway to get SAS to see the files (which I believe are present) or is a re install required?
... View more
08-22-2014
10:05 AM
Thanks for the response Hai.kuo, you were right I hadn't verified installation. When I run PROC PRODUCT_STATUS on their machine the only component I receive information back on is Base Product. They seem to have all of the proper components installed, at least when I look through the Program Files folder. Is this just a case of SAS not seeing this and there is a way to update it or will SAS need to be re installed? We had IT reinstall it on another machine that seemed to be having the same issue (I haven't looked at that machine so I can't be certain) but that didn't resolve that user's issue so that's why I ask.
... View more
08-22-2014
08:53 AM
Some of our users are getting the error: The ODBC engine cannot be found. Error in the LIBNAME statement. The also get the same error when trying to use the TeraData engine as well. I've checked their installations and confirmed that they have both the licenses needed to use these engines as well as the .dll files required. We have a standard installation for SAS so my thought is that their SAS installation isn't the issue here, and that it's possibly something else on their computer. Any suggestions on what could be causing this issue?
... View more