It is, as I predicted, 2 years ago. VA looks like a great product, and if you have the money and the time, I would suggest you move over to using VA now, before being stuck with an obsolete platform. Nick ... View more

The great thing about Enterprise Guide is that you can use point and click to create graphs and learn about the code that is produced at the same time. Let EG do the heavy lifting. Coding from scratch is so last century. Try it. ... View more

Try this link http://www.pharmasug.org/proceedings/2012/DG/PharmaSUG-2012-DG03.pdf. Its for EG 4.2, but the functions are pretty much the same in 6.1 ... View more

Hi, Not sure of your requirements here, but the select statement produces a report output. Exporting to csv requires an actual dataset. Is there a reason why you are directly coding a select statement not using a create as well? On the other hand, you can send a report to Excel if you have AMO installed. Nick ... View more

You can also use the 'Assign Project Library' task under the Tools category in the Task List. ... View more

Hi, SAS EG 6.1 treats Excel the way previous version have. The point of EG is not to be an Excel viewer, but to interface with Excel so that it can import that data, and be able to carry out the advanced analytics that Excel can't do. Similarly, it can send SAS data and output to Excel and Word, although, in the latter case, you might have to do some resizing and reformatting, and this is perhaps what you don't like. A warning however that the 64 bit EG will not be able to interface with 32 bit Office unless AMO is installed. More importantly, 32 bit Access files will not be able to imported with 64 bit SAS EG, and forget about .dbf files. There is a 32 bit EG out now, but this does not have a stand-alone installer yet. Perhaps someone can clarify when this might be released? If you want to view and work with SAS datasets within Excel, AMO, as suggested by Jaap is more appropriate, but, you will need the BI license for that. ... View more

Hi, I can confirm, having done the exam 4 weeks ago, that there are not. Displaying windows, AF and DDE are legacy and deprecated capabilities (and I would hope that SAS would not encourage such things by testing it!), There was however a question on data step debugging (a very simple one at that), and that is about the only thing a SAS EG person would not know about. Nick ... View more

Hi, I disagree. We no longer save SAS EG in metadata after our content server became corrupted and we were unable to recover our projects because there is no easy way to backup and restore the content, especially if you want to restore individual projects. My recommendation is that unless searching and impact analysis is very important, never save your projects in metadata. Nick ... View more

Hi, I have recently used SAS EG and the book you have mentioned, and can't see any limitation as long as you do everything in a code node. Perhaps you can be a bit more specific about the problems you are having. ... View more

Thank Chris for the clarification. I also note similar issues with access Microsoft Access databases. It is a shame that this capability has been removed, and no effort to continue support and compatibility. I know it is difficult to keep everyone happy, but perhaps more explicit documentation of such changes would be helpful to prepare users and help inform decisions about whether to upgrade to a newer version of EG. Thanks, Nick ... View more

Hi Patrick, Yes, I have confirmed with tech support, and the help in 6.1 does not list dbf as a supported type. One of our users noticed that the .dbf option was not listed as an importable type in the wizard, and, when you use all file types and try import a dbf it throws up an error. Of course, proc import works, but that is not the point. Not sure why this support was removed. Nick ... View more

Hi Chris, Thanks for your response. However, I think that there may be a bug in this process, as the RegAddin.exe doesn't seem to do anything when running it from the AMO installation folder, and besides, the xml file in the BIClientTask\4 directory has no information in the tags that the custom task has been registered in AMO as apposed to EG. Therefore, no matter what you do, the Task Import wizard runs the one time, and only seems to bring about EG capabilities in metadata and not AMO capabilities. The documentation on SAS Support is also obviously deficient as it seems to be a straight out copy of the EG version, so unless the one process of using the Task Import wizard brings about the necessary changes for both AMO and EG in metadata, I think I am stuck. It is also a poor design to not be able to de-register the custom task in metadata and I would hope that SAS provides a mechanism for this. It is not ideal to clutter up metadata with capabilities that have no use. I am assuming I am one of few to have tried this, but if someone has managed to make this work, then, it would be great to share how they managed it. I will forward this on to tech support and see if they can do anything. Thanks again, Nick ... View more

Thanks Michelle, The problem is more about the fact that the custom task doesn't seem to be registered in metadata for the AMO roles (although it is registered for the EG roles) rather than implementing role based access. Regards, Nick ... View more