Tuesday, November 6. 2007Not enough room for all of that dust and data? Our SAS usage notes usually do a great job of matching symptoms to solutions. But good old SAS note 10751 really stretches the limits of logic.The symptom: a message during the SAS 8.2 setup process that says "string variable is not large enough for string". The solution: "To circumvent the problem, clean the CD with a soft cloth." Hey, it works. Fortunately, this sort of problem will be dusted away with electronic software delivery in SAS 9.2. Thanks to Armistead (quoted in the ESD article) for bringing my attention to this SAS note. He keeps a framed copy of the note in his office; I'm sure he's looking forward to the day that he can retire it from the knowledge base. Comments
Display comments as
(Linear | Threaded)
Hey Chris, I got a problem when I run the data process. When I set two or more data together, if they have variable that have same variable name but different variable length, the generated variable's length will be aligned to the shorter one. This also happens even when I pre-format the short one to be the same format. I have no idea how to deal with this situation. I notice that there 3 attributes for each variable: Len, Dlen, Format. What's the difference of them? How set these attributes? Thanks!
Although it's not really related to this blog entry, it is a good question. I'll attempt to address it in another entry.
I miss working for SAS.
That Note, sounds familier. Many a time I solved and instalation problem by ordering a new set of flopy disks, disckes, CDs. The ESD sounds great. I wonder how many would avoid using it so as there is no track of how many instalations they performed. I know this falls in the gray area. In my time the licence was per user and we did not mind how many pcs were intalled (sas/austria & sas/Denmark that is). All the best to the guys holding the fort. Eli |
ABOUT CHRIS Chris Hemedinger is a senior software manager in SAS R&D. He's part of the team that builds SAS Enterprise Guide and SAS Add-In for Microsoft Office. He's also co-author of the popular SAS for Dummies book and moderator of the SAS Enterprise Guide discussion forum.
Syndicate This BlogSubscribe by E-mailQuicksearchOther SAS BlogsBI and Chicken Pot PieConversations and Connections Data Flux Community of Experts Closing the Intelligence Gap In Other Words In the Final Analysis JMP Blog Key Happenings at support.sas.com The New Lending System The Text Frontier SAS Global Forum Blog sascom Voices Blog A Shot in the Arm All SAS Blogs Recent postsJob security through code obscurity
26Jul2010 Hope for ugly programs 14Jul2010 Using Gmail to send a message via SAS Enterprise Guide 12Jul2010 Once more, with feeling 08Jul2010 Thinking economically 28Jun2010 SAS Professionals know how to party 24Jun2010 Hatching success at SAS Professionals 15Jun2010 My Out of Office reply for 12June-20June 11Jun2010 Let's call the whole thing off 11Jun2010 Crayon guide to DATA step merges (and other links) 09Jun2010 BOOKS & VIDEOS SAS for Dummies -- If you want to learn to be productive using the latest SAS tools and technologies in your daily work, but don't necessarily want to learn SAS programming, then this book was written for you!  Efficient Data Access with SAS Enterprise Guide (YouTube) -- Shows the best way to access data in a DBMS from SAS Enterprise Guide, using M&Ms as a prop.  Exciting combinations: SAS and Microsoft Office (YouTube) -- A metaphor for the exciting features you get when you add the SAS Add-In for Microsoft Office to your desktop.
The blog content appearing on this site does not necessarily represent the opinions of SAS. Your use of this blog is governed by the Terms of Use.
|
A reader from Bejing commented on a recent post with a question about data lengths and formats. While that wasn't really related to my post, I thought I'd attempt to answer in a new entry, here. The question is basically this: when I combine two data
Tracked: Nov 20, 14:30