- #SAS UNIVERSITY EDITION SET LIBNAME PATH ON MCBOOK FREE#
- #SAS UNIVERSITY EDITION SET LIBNAME PATH ON MCBOOK WINDOWS#
I have not been able to find reference to this known bug so any help like what is the safest way to interrupt EG at this point would be greatly appreciated. I tried to recapture the EGP from the location assigned as the Project Recovery area on Windows, but the only thing saved there, was the last copy of a program I had last executed, nothing else from the EGP. EGP was lost and unfortunately our IT is not doing backups of SAS-related files in this filesystem at a new data center. EGP file disappeared from the folder directory as I viewed it on Linux.
I was also prompted to save an autocall macro to it's original location, which I did. EGP would be autosaved, so I re-entered EG and chose the Autosave to the.
#SAS UNIVERSITY EDITION SET LIBNAME PATH ON MCBOOK WINDOWS#
The first, I could find no way to interrupt the hung EG session except to End the process from Windows Task Manager. I'm afraid I've run into the gotcha as was noted in the original post when trying to "view" the xlsx sheet while in EG. To whom are you listening in those cases? To agree I hope you see the same kind of conflict interest of the "users end-users" and "users ts-support and audit - decision makers" is there. There is an aes option added with 9.4 for sas datasets. But at some moment there will be the functionality requirement of data having being encrypted. To much to solve first with higher prio's. That are user functionality requests and not the same as IT-people requests for blocking that. I think that would be no problem with a nice sftp browser associating the xlsx with Excel and processing it all server-side with SAS. They want to have it being delivered and accessed as easy as on their windows desktop. The first and most difficult part is getting acceptance for those XLSX interface on the Unix area.
Personal I have the experience that an Excel is often getting the primary concern instead of the data-analytics area. Some users are wanting that as primary interface, others have replacements not wanting to use MS. I am remembering your "autoexec" EGuide post.Ä¢/ The Excel (better MS office) question is having the same background. The feed-back with ideas it a good one but do not forget doing a root cause. There is a difference that is doing root cause analyses. WANT MORE GREAT INSIGHTS MONTHLY? | SUBSCRIBE TO THE SAS TECH REPORTÄ¡/ Customers do not always tell the things they are really needing but instead telling things they are having some difficulties with. If you have SAS 9.4 Maintenance 2 or later, try it out! Let me know how it works for you by sharing a comment here. I have found LIBNAME XLSX to be a quick, convenient method to bring in Excel data on any SAS platform.
#SAS UNIVERSITY EDITION SET LIBNAME PATH ON MCBOOK FREE#
For these reasons, I recommend using DATA step to copy the Excel content that you want to another SAS library, then CLEAR the XLSX library to free the lock on the Excel file. Some techniques to MODIFY the data in-place will not work. The engine starts at the beginning of the file and continues in sequence to the end of the file. One other IMPORTANT caution: The XLSX engine is a sequential access engine in that it processes data one record after the other. If you need that sort of flexibility, you can use PROC IMPORT to provide more control over exactly what Excel content is brought into SAS and how. Also, you won't see the familiar "$" decoration around the spreadsheet names when they are surfaced in the library within SAS. For example, the XLSX engine does not support Excel named ranges (which can surface a portion of a spreadsheet as a discrete table). The XLSX libname is different from the EXCEL and PCFILES engines in other ways.
Remember, you can also create Microsoft Excel files with Base SAS by using ODS EXCEL (as of 9.4 Maintenance 3). Here is my output in Microsoft Excel with all of these data sets now as sheets: Libname xlout XLSX '/folders/myfolders/samples.xlsx'