Update in case anyone else is still struggling with this - at my organization it turned out to be a need to apply updates to Microsoft Office. Once all the Microsoft updates were done, SAS could once again export to Access without the file already in use problem.  ... View more

@Michelle  Can you copy and paste what you see in Studio's About dialog? Click the ? in the banner in the top right and click About Studio. Copy and paste any non-company sensitive information.   A couple of suggestions:   Can you try using another browser to see if you get the same issue?  Have you tried clearing your browser's cache as well?  Did this happen mainly when you copied from some app like Notepad++  and pasted it into Studio?   Samantha DuPont UI Designer on SAS Studio and SAS Enterprise Guide ... View more

@RahulG Of course! Thank you so much for reading! This is just the first task post in a series called Custom Task Tuesday. Check out some of the other articles if you're interested.  ... View more

  In 9.4m5, we will introduce a new style called HTMLEncore. It will be a child of HtmlBlue but with more readable font-size and fonts. It will be available with SAS Studio 3.7 which should be released sometime in the 4th quarter 2017.  ... View more

@Michelle, that's so great to hear! I think the Custom Tasks are a perfect solution to your problem, and the XML is easier than you think. If you have questions about specific errors, let me know! ... View more

Hi Michelle,   With "parallel sessions" I meant two or more instances of SAS open at the same time, not one session after the other. This would give you two (or more) physically separate work folders, hence two physically separate formats.sas7bcat files.   The size of the format catalog does not seem to be an issue in your case.   Using a different configuration file should be no problem, I think, as long as you can copy the existing sasv9.cfg to any other place. However, you don't even need a different .cfg file to change the WORK system option. According to the documentation, "the options that are specified in the SAS invocation command" are processed at such a late stage, that they can override the settings in all existing configuration files. So, you can simply call SAS like this: "C:\Program Files\SASHome\SASFoundation\9.4\sas.exe" -WORK "X:\your\path\to\SASwork" (This would be the content of the "Target" field of the "SAS Properties" dialog box, of course with suitable paths.)   I've just tested it and, indeed, SAS created the session-specific work folder at the new location. My idea was to rule out potential (hardware?) issues with the disk where your work library is normally located. ... View more

The BI server that is working on top of SAS/Base (Foundation). It is an extension on SAS integration technologies as there is a metadataserver added using an objectspwaner. By that there is move to Server-side processing an not local on your desktop.   ... View more

@Lee (no not for Michelle question directly).... Seen your role, thanks for your attention. I always had some questions related to capacity management (ITIL context) ... 1/Why is SAS using that a complicated approach with the software depot and installing from there. It is requiring almost always a reverse engineering to get it into required processes that SAS is not recognizing. 2/ the msi options for some parts (base eguide amo) with 9.4 are helpfull but imo more is to be done. 3/ SAS studio, the java clients DI EM etc are zero impact for Windows not needing a msi package this would make a lot things easier. But why introducing browser dependencies? I do no expect answers in this thread. ... View more

Thanks Jaap & Eric, finding out what our SMTP server domain name got around the MAPI problems! Our SAS admin doesn't actually use SAS so I think he is not so familiar with some of the issues (and my whining is not high on his priority list :smileysilly: ). ... View more

Technically, the lower down select is something executed in SYBASE, while the earlier select is a SAS statement that is selecting from the cursor or whatever it's called returned from SYBASE.  Most commonly passthrough is used by people who are more comfortable (or at least, are very comfortable) in the passthrough language (ie, SYBASE in this case) and are happy to do all the work in the passthrough language (hence the select *) - but there's no rule that you have to.  You can do WHERE statements and such as well in that outer query. ... View more