In this case, I learned that SAS for Windows 9.2 would allow me to import that Excel file in a place and form that I could actually use, once I mastered a bit of the SAS lingo. The problem was that I just needed straightforward instructions on getting that Excel data into SAS and working with it, and they were all assuming that I understood half of what they were saying before I started, and really only needed the other half that they happened to be providing.įortunately, even a completely clueless individual is apt to learn something, if only by accident, if s/he stays around long enough. They were all well-written and completely useless. These included the built-in SAS help system, many webpages, and SAS guides by Evans, someone at Cornell, and others. I flailed around for several hours, looking at random sources of potential guidance. I didn’t keep detailed notes in the early phases, so some of my comments here are a bit jumbled. I decided to stick with the older format, just in case. SAS did seem willing to try to import an. That advice was more than a year old at this point, and may not have been accurate anymore. The situation would probably have been simpler if I had been attempting the import on campus, but I wasn’t.Īs initial preparation, someone advised that it might be best to save that data in Excel 97-2003 format, because SAS was not yet up to the challenge of importing from Excel 2010. To use SAS, I was connecting with a university computer via some uncertain combination of software referred to as Citrix, vDesk, and VLab. That is, I was working on my home computer, where I did not have SAS. I was using SAS 9.2 in a remote environment.

Import excel into sas jmp