Date: Sat, 15 Oct 2005 06:59:22 -0600
Reply-To: Alan Churchill <SASL001@SAVIAN.NET>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Alan Churchill <SASL001@SAVIAN.NET>
Subject: Re: Reading SAS data into Excel using ODBC
In-Reply-To: <434f744c$0$13958$5a62ac22@per-qv1-newsreader-01.iinet.net.au>
Content-Type: text/plain; charset="us-ascii"
Scott,
I tried to send you an email direct but got a kickback.
I have an unpublished paper that might shed some light on this area. It's
not ready for primetime otherwise I would publish and send out on SAS-L.
Contact me at your convenience if you want to get a preliminary copy.
Alan Churchill
Savian "Bridging SAS and Microsoft Technologies"
www.savian.net
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Scott
Bass
Sent: Friday, October 14, 2005 3:05 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Reading SAS data into Excel using ODBC
Thanks Wensui. I've never created a *.udl file, but perhaps a bit of
Googling would educate me. However, as I mentioned in my post below, the
staff in question don't have SAS installed on their machines.
"Wensui Liu" <liuwensui@GMAIL.COM> wrote in message
news:1115a2b00510131445j30acda1bw1ad15c68d9301f6d@mail.gmail.com...
> Scott:
>
> If I were you, I would create a *.udl file to use OLEDB linking to SAS
> data
> from Excel. By doing so, your coworkers don't need to create local DSN at
> all. What you need to do is to distribute the *.udl file to your coworkers
> as long as they have SAS installed on their PCs.
>
>
> On 10/12/05, Scott Bass <usenet739_yahoo_com_au@alfredo.cc.uga.edu> wrote:
>>
>> SAS 9.x
>> Windows 2000 Professional
>>
>> Summary: Staff in my deparment, who don't have SAS installed on their
>> computers, have need to read SAS data into Excel for further analysis.
>>
>> Details: For the sake of brevity, I will only summarize what I've done. I
>> can do what I want if I create a User or System DSN, then open that DSN
>> (in
>> C:\Program Files\Common Files\ODBC\Data Sources) in Excel. This pops up a
>> window where I can select the dataset of interest. Alternatively, I can
>> open My Documents\My Data Sources\+Connect to New Data Source.odc in
>> Excel,
>> create an ODC file, and accomplish the same thing. I've gotten this to
>> work
>> with both a local server or SAS/Share server (running on my local
>> machine).
>>
>> Problem: My colleagues will want to do this without creating any DSNs on
>> their machines. To test this, when I copied the DSN file to a network
>> drive
>> and accessed them from another computer, it failed. Perhaps that's why
>> they
>> are called "(non sharable)"? If I try to create a DSN under the File DSN
>> tab, I cannot create settings in the Servers and Libraries tab of the SAS
>> ODBC dialog.
>>
>> I have read the SAS ODBC Driver: User's Guide and Programmer's Reference
>> doc.
>>
>> Questions:
>>
>> 1. Can this even be done, or are local DSN definitions required for every
>> user that needs to access the SAS data?
>>
>> 2. What's the difference between a DSN and ODC file? They seem to
>> accomplish the same thing.
>>
>> 3. How can I create a File DSN where I can specify the Server and
>> Libraries
>> during definition?
>>
>> 4. The ODC creation process (using Microsoft OLE DB provider for ODBC
>> Drivers), in the Data Link Properties Window, Connection tab, has the
>> Connection String field. Can someone provide a typical connection string
>> without using a DSN?
>>
>> 5. Bonus: we have a SAS/Share server running on a Unix box (on the other
>> side of the world). It would be cool to connect to that SAS/Share server
>> and download the data from there into Excel. What do I need to do to
>> connect to that server? Do I need to know the port it's listening on? Do
>> =
> I
>> need to edit my local services file? Etc.
>>
>> Thanks,
>> Scott
>>
>
>
>
> --
> WenSui Liu
> (http://statcompute.blogspot.com)
> Senior Decision Support Analyst
> Cincinnati Children Hospital Medical Center
| 
