Our organization is currently in the process of migrating from Windows XP. As you may know, the path to a user's documents folder changes during that migration, from C:\Documents and Settings\<userid>\My Documents, in XP C:\Users\<userid>\My Documents in Win 7 One of our SAS users has a lot of data -- including SAS datasets, .csv files and other external files, in her My Documents folder, and she has written a lot of programs with INFILE and LIBNAME statements that point to the XP path: c:\document and settings\... When she moved to Win 7 she expected to have to change the paths on all these statements, but she tried running a program anyway -- and it worked. The program found the datasets and libraries in the C:\Users locations. But, strangely, the logs and properties pages all showed the files at physical locations on the c:\documents and settings path. I'm not complaining -- I think it's pretty cool that SAS is smart enough to convert these paths on the fly -- but I wonder if someone can confirm my analysis of what happened, so I can reassure my user that her programs really are working correctly. ... View more

I suspect the answer is NO. But let me describe our situation. Currently we have Windows XP on our workstations. Some of these users run SAS 9.1.3 locally, while others user EG 4.1 to access SAS 9.1.3 on an Enterprise Business Intelligence server. We are about to migrate all our workstations to 64-bit Windows 7, which means we will have to upgrade to SAS 9.2 and EG 4.2 (or 4.3) on our workstations. No problem with this -- except that EG 4.2 does not connect to SAS 9.1.3 on the remote server. At this point, we do not have the option of upgrading SAS on the server to 9.2. It looks to us like this means that our EG users will not be able to access SAS on the server. This could be a traumatic and expensive situation for some of our users. Is there a workaround that we might be able to try? ... View more