Date: Wed, 2 Nov 2005 22:15:52 -0600
Reply-To: Dimitri Shvorob <dimitri.shvorob@VANDERBILT.EDU>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Dimitri Shvorob <dimitri.shvorob@VANDERBILT.EDU>
Subject: Re: Import/export PC files and SAS/ACCESS interface
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
You might not be able to import Access variable labels this way; once
facing the same task and not having SAS/Access or StatTransfer, I ended
up writing a simple Visual Basic macro that I have since posted to SAS-L.
>I think PROC IMPORT will meet your needs. It as simple as
>proc import datafile="c:\sheet.xls" out=lib.dsname replace dbms=EXCEL;
>or DBMS=MSACCESS or CSV
>"Libertyblle" <Marlene.Scott@medstar.net> wrote in message
>>I probably should have been a *tad* more explicit.
>>A majority of the time (90%-95%), the need for our group is to import
>>MS Access/Excel tables into SAS. The bulk of the
>>statisticians/epidemiologists on staff here primarily use SAS to
>>perform the bulk of their data analyses/modelling. It is the rare
>>occassion where I use SAS to export data into MS Access or Excel.
>>The problem is that since we switched to using SAS v9 a few months
>>back, decisions were made as to which modules to keep/jettison due to
>>cost constraints. My understanding (limited) is that in order to
>>import PC files, one needs to have the SAS/Access interface module
>>installed. Is this correct? According to the technical documentation
>>read thus far, my hunch is this component is necessary. This hunch was
>>strengthened when I submitted the LIBNAME statement as part of Wensui's
>>code and got a message stating the OLEDB engine could not be found.
>>What I wish to know is if my hunch is correct or if there is an
>>alternative method I can use to directly import into SAS. If no
>>alternative exists, then my manager and I need to have a serious
>>discussion with management about the cost-benefits, in terms of both
>>time and money, about doing without it.
>>Thanks to all for your imput.