HP have announced that they will buy EDS (which in sunny New Zealand is like the mouse eating the elephant)
I have posted before that I think SAS will eventually be brought (or merged) and that HP was a strong contender.
Well consuming EDS will take a lot of time and money, so will this create an opportunity for somebody else to make the move while HP is busy?
SAS has just announced that Enterprise Guide is now certified for Microsoft Vista over on their blog.
I can understand why you would install and run SAS Enterprise Guide, but haven’t quite seen the value in Vista, thank goodness Dell now ships there PC’s with Windows XP.
Now if only SAS would release Enterprise Guide for my Mac (5% market share and growing 
I have finally got around to reading SAS for Dummies by Stephen McDaniels and Chris Hemedinger (well I flicked through it at least).
One of the tips has ended up saving me a lot of time lately.
When you are in Enterprise Guide and you have large flows in the project designer, you also typically end up with a large number of tables, result, logs, code blocks etc open as well as individual tabs.
The downside of this is it is a hassle scrolling left to go back to the procces designer view.
I thought I was being clever when I worked out I could just click on the project explorer view and then on project designer at the top of the tree.
Well all you need to do is press ‘F4′ and you will be taken to the project designer windows faster than a F1 Ferrari.
I have talked to a number of customers that are having a problem with the SAS Addin for Microsoft Office (AMO) remembering a users password and then locking them out of their account.
When a user configures their connection to the SAS Server in AMO they can save their password, so they effectively gain a form of single sign on. (The password is stored as an encrypted text string in an XML file).
A number of customers I talked to also have some form of LDAP authentication setup (i.e. Active Directory), Unfortunately when a user changes their password on the LDAP server, AMO doesn’t know about it. It keeps trying to authenticate the user with their old password until the users account gets locked.
SAS Enterprise Guide also enables the user to store their connection credentials, but it seems to prompt the user to re-enter their credentials if the authentication with the server fails, therefore the users account doesn’t get locked.
We are working through some work arounds for this to see if we can fix the AMO issue, but has anybody else struck this?
Anybody else fixed it?