The top gotchas when moving to 6. SAS for Windows. Many SAS customers are quickly adopting 6. Microsoft Windows, and they are pleased- as- punch when they find a 6. SAS to run on it. They waste no time in deploying the new version, only to find that a few things don't work quite the same as they did with the 3. This post describes the top snags that end users encounter, and how to work around them. Gotcha #1: Importing Microsoft Excel files. Imagine you have a program that looks like this: proc import out=work. It can happen when you use PROC EXPORT to export Excel files, or use DBMS=ACCESS for Microsoft Access database files, or when you try to use LIBNAME EXCEL to reference a local Excel spreadsheet as data. The Cause: Your 6. SAS process cannot use the built- in data providers for Microsoft Excel or Microsoft Access, which are usually 3. In a previous blog post, I've provided a bit of explanation about this limitation. The Fix: Use DBMS=EXCELCS for Excel files, or DBMS=ACCESSCS for Microsoft Access. For LIBNAME access, try LIBNAME PCFILES. Doodle jump pour vivaz gratuit Aliena from tankspot owned 06-7730-8360 fax Hector lavoe quotes Super kush botanical potpourri side effects Hot stuff seamless female. The R Project for Statistical Computing Getting Started. R is a free software environment for statistical computing and graphics. It compiles and runs on a wide. These approaches use the PC Files Server, which is a separate small application that is provided with SAS/ACCESS to PC Files. Note that you may need to go back and install this application, as it might not have been placed in your installation automatically. However, you can use the Autostart feature to skip having to configure it as a service, and thus minimize the changes to your SAS programs. Alternatively, you can try DBMS=XLSX to remove the data providers from the equation. NOTE: There are a few feature differences between the EXCELCS and EXCEL options. That works, but it might introduce other incompatibilities with how you use your Microsoft Office applications. Microsoft recommends the 6. Office in only a few circumstances; consider the implications carefully before you head down this road. Gotcha #2: Incompatible FORMATS catalog. SAS Voices RSS News and views from the people who make SAS a great place to work; Customer Intelligence RSS.
Suppose that you have a library of user- defined formats that you once created by using PROC FORMAT. User- defined formats are stored in SAS catalogs, which are a sort of SAS- specific file system structure that SAS can access during your session. If you created and used these user- defined formats with 3. SAS, you'll see this message when you try to use them with 6. SAS: 1. 5 libname library . Even though you've just moved from one version of Windows to another, from a SAS perspective these files are different, with different internal structures. The Fix: SAS provides the utility procedures CPORT and CIMPORT to allow you to transfer catalog content across different operating environments, and you can certainly take that approach for this scenario. If you have a mixed environment on your team where some people have 3. SAS and others have 6. SAS, it might be easier to decompose the format definitions down to data sets (by using PROC FORMAT and the CNTLOUT option). You can then easily recreate the formats . That brings us to the last . But you might see a message like this: NOTE: Data file TEST. HMEQ. DATA is in a format that is native to another host. However, you might not have expected it to kick in when you upgraded to 6. SAS on Windows. The Cause: SAS data set files are written with an encoding that is specific to the SAS operating environment. In 3. 2- bit SAS on Windows, the encoding is WINDOWS. On 6. 4- bit SAS, it's WINDOWS. When the data set encoding differs from the native SAS session encoding, CEDA kicks in. The good news is that in SAS 9. SAS developers . And if you have SAS 9. SAS for Windows. If you decide to convert entire data set libraries to the new native encoding, you can achieve this by using PROC MIGRATE. Parting bits. I'll finish this post with just a few general points to guide you: 6. Windows is pervasive, and is a Good Thing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |