What have you tried so far? ... View more

Even worse. Unlike the 'supreme' court, I'm convinced that companies are comprised of people. ... View more

Thanks, Chris. I think a better solution would have been to host the archive of sascommunity.org within the communities.sas.com website...no cost to manage at all. I think I suggested years ago that SAS have the ability to write to a range (since it can *read* from one)...maybe fix that damned white space bug at the same time...:( ... View more

I ***HATE*** when companies do that. They should just keep the old pages and set them to read-only. grrr... ... View more

that looks more promising...I'll give that a try...thanks. I wonder what happened to that wiki site and why it was nuked... 😞 ... View more

That's where I started. It refers to the missing wiki link. WHERE TO GET THE MACRO We did our best to only include carefully written and tested code, but the code may have to be updated from time to time to correct for errors or enhancements that we or others might discover. Additionally, while a copy of the macro is included in this paper, copying and pasting from a pdf file often introduces stylish looking quotation marks which aren’t correctly recognized by SAS. As such, we created a page for the paper on sasCommunity.org. The page includes copies of the source code and updated versions of this paper. The page can be found at: http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export ... View more

Isn't 'programming' way too generic? It really isn't even applicable and is misleading. EG and Studio are more 'environments' or 'applications' or 'shells', like Excel, Word, Quicken or Appleworks. ... View more

Problem is, combining unrelated boards causes clutter. If someone doesn't use EG, they probably don't want to see posts about it. Likewise, if they want to find out about SAS Studio, they can go to that board. The whole point of separate boards is to help us find a specific board related to our problems, questions or suggestions. ... View more