Prev: Tagsets.excelxp Password protect excel worksheets
Next: software engineering
From: Craig Johnson on 5 Nov 2009 10:34
Tried importing an excel file with no luck. A coworker with the same set u=
p
tried to work with access and excel with the same results. After she did a
little digging she found that the excel import issues was due to using a 64
bit version of SAS. It seems the 64 bit version has some tweaks that the 3=
2
bit doesn't. For example, rather than dbms=3Dexcel you use dbms=3Dxls. SO=
Ooooo
per SAS's instructions (http://support.sas.com/kb/33/228.html)......we can
either rewrite our code to work in 64 bit SAS or

"Option 2

You can leave the 64-bit version of SAS installed and also install the *
32-bit* version of the SAS=AE System for Windows so that PROC IMPORT and PR=
OC
EXPORT work with Excel and Access files the same as they do in SAS 9.1.3.
However, the 32-bit version is limited to 4 gigabytes of memory. Both
versions can be installed on the same machine and do not interfere with eac=
h
other. "

Seeming these desktops only have 4 gigs of ram and no one wants to rewrite
code, we are just going to install 32 bit SAS. FYI once I converted back t=
o
32 bit the libname statements worked as expected. My guess is that the 64
bit has something wrong with the install and tweaks may need to be made in
the SAS code but........at this point there is no real benefit for us to us=
e
the 64 bit.....
First  |  Prev  | 
Pages: 1 2
Prev: Tagsets.excelxp Password protect excel worksheets
Next: software engineering