Date: Mon, 24 Mar 2008 09:03:18 -0600
Reply-To: Alan Churchill <savian001@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Alan Churchill <savian001@GMAIL.COM>
Subject: Re: FW: Import Excel Into SAS
In-Reply-To: <B8019A936BC.00000127tomvincent@inbox.com>
Content-Type: text/plain; charset="iso-8859-1"
Pick the SAS editor, they are all about the same.
Yes, Microsoft products produce documentation for custom code. It is system
documentation and is an included feature in Visual Studios. Google
SandCastle for details.
I didn't misspell Intellisense. Google it as well to see how it works,
however let me provide a brief overview. Intellisense automatically prompts
a programmer for the next term based upon a set of choices. For example, it
would allow you to type proc and automatically the editor would bring up all
installed procs so you could use the arrow key to select one. Then it would
prompt you for all choices within that proc and so forth. It is a MAJOR boon
to developer productivity and greatly reduces coding errors.
Visual Studios is probably the finest editor on the planet. A little bit of
reviewing Microsoft's feature set would be helpful to SAS and then a
commitment to implement at least a portion of those features...Intellisense
being the top one.
Alan
Alan Churchill
Savian
www.savian.net
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Tom
Vincent
Sent: Monday, March 24, 2008 6:39 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: FW: Import Excel Into SAS
Which SAS editor are you talking about? If it's Base SAS, the coder is
responsible for the things you're talking about. Even in EG, the coder is
responsible for documenting & commenting custom code.
Are you suggesting that Microsoft products produce documentation for custom
code? What products are those?
And misspelling 'intelligence' doesn't help your case much. :)
-*-*-*-*-*-*-*-*-*
Tom Vincent
"Proudly Wicked Since 1974"
-*-*-*-*-*-*-*-*-*
I want to move on from evidence, which is a good reason for believing
something, and warn you against three bad reasons for believing anything.
They are called 'tradition', 'authority' and 'revelation'.
- Richard Dawkins
The rich are destroying America. Support a $250K MAXIMUM wage and a LIVING
wage for the poor.
Due to deliberate damage by Yahoo, my new e-mail address is
TomVincent@Inbox.com - Boycott Yahoo!
"What are we gonna tell the sheriff, sweetheart, that a Kryptonian girl
vaporized a federal agent?" - Jonathan Kent
> -----Original Message-----
> From: savian001@gmail.com
> Sent: Mon, 24 Mar 2008 01:41:16 -0600
> To: sas-l@listserv.uga.edu
> Subject: Re: FW: Import Excel Into SAS
>
> I am disheartened by the lack of Intellisense, code commenting, code
> documentation, refactoring, and a whole lot of other aspects of the SAS
> editor. I know Audi has done a good job of trying to put these into the
> product but SAS R&D should improve the editor to make SAS easier to code.
>
> When are we going to get the monkey boy dance from SAS screaming
> "developer,
> developer, developer...."? If you are unfamiliar with the term, just
> google
> it along with Ballmer.
>
> Microsoft places developers at the top of the pecking order. It makes
> coding
> easier and improves productivity inside and out. SAS should place a
> greater
> emphasis on developers as well and make a better editor. For developers,
> SAS
> has a lot to learn from Microsoft in this area.
>
> Alan
>
> Alan Churchill
> Savian
> www.savian.net
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> Stephen
> McDaniel
> Sent: Sunday, March 23, 2008 11:44 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: FW: Import Excel Into SAS
>
> Hi Audi,
>
> The next release of EG will support Office 2007. Unfortunately, due to
> the
> extended time it takes between major releases at SAS, the old EG doesn't
> support Office 2007 which wasn't production as of EG 4.1 release. SAS
> 9.1
> XML support is available programmatically but isn't terribly flexible or
> easy IMO, EG doesn't have it at all. EG does import and export from
> multiple database and file formats.
>
> I would have to respect your opinion on the process flow in EG, but I can
> personally tell you that many people love this feature and use it
> exclusively. Some even consider it the reason to have adopted EG 4.1.
> If
> you don't like the feature, it can be easily turned off. That said, a
> major
> feature in Visual Studio that is lacking in SAS DMS and EG is the
> Intellisense type of logic in VS and in Excel 2007, this would make
> programming much easier in SAS. Also, it would be really cool if EG
> would
> let you drag and drop datasets and column names straight into the code
> window!
>
> As someone who is constantly joining tables and prepping data for
> analytics,
> I would say the EG process flow is usually pretty nice, occasionally out
> of
> hand, but overall a major plus IMO.
>
> Best,
> Stephen
>
> -----Original Message-----
> From: Audimar P. Bangi [mailto:audi@sas2themax.com]
> Sent: Friday, March 21, 2008 11:30 AM
> To: Stephen McDaniel; SAS-L@LISTSERV.UGA.EDU
> Subject: Re: Re: FW: Import Excel Into SAS
>
> Here's my take on Enterprise Guide:
>
> There are some limitations:
>
> o It cannot read Microsoft Excel 2007 workbooks.
>
> o It cannot export a multisheet Excel workbook as separate SAS datasets
> in
> one passing. You have to open each worksheet (table) one by one and save
> them separately as SAS data sets.
>
> o It cannot export SAS output as a multisheet Excel workbook.
>
> o It cannot save SAS data sets as Excel XML spreadsheet.
>
> On the Project Process Flow:
>
> I think that this feature is unnecessary, and confuses more than it helps
> the user. "Recording" every user's action as a process flow is not
> necessary, especially for actions like adding a new project item,
> importing/exporting a data set, etc. In the end, the Project Explorer is
> clogged with so much junk that it becomes hard to make sense of what the
> project is all about.
>
> A better IDE design is that of Visual Studio, from which the Project
> Explorer/Manager of my Notebook Professional is based. GUI is more
> intuitive
>
> and user-friendly.
>
> Some pros:
>
> o You can do stastitical analysis and charting.
> o It can import various types of databases.
> o You can write your own EG add-in (albeit easier said than done!).
>
> Audi
>
>
> ----- Original Message -----
> From: "Stephen McDaniel" <stephen@STEPHENMCDANIEL.US>
> To: <SAS-L@LISTSERV.UGA.EDU>
> Sent: Friday, March 21, 2008 12:34 PM
> Subject: Re: FW: Import Excel Into SAS
>
>
>> Or, if you have PC SAS 9.x, then you can ask to have Enterprise Guide
>> installed on your PC and import/export to Excel with a point and click
>> wizard that is quite simple...
>>
>> Regards,
>> Stephen
| 
