On Mon, 30 Sep 1996 19:46:31 -0700, Andrew James Llwellyn Cary <ajlcary@ix.netcom.com> wrote:

>The SAS ODBC server is (at least last time I looked) distributed by the >SI as part of SAS/BASE. The SAS/ODBC client is distributed as part of >SAS/Access to ODBC. > >This means that you only need to have the SAS/BASE product to allow >(for example) MS-Access to read your SAS datasets via ODBC. > >You have to have the SAS/Access for ODBC to read MS-Access datasets from >SAS via ODBC. > >SAS will send you both 32 bit and 16 bit ODBC drivers (you must use the >16 bit drivers with Win3.11+Win32s) if you request. They used to be free >with the base product. >-- >Andrew J. L. Cary | I Reckon that the Opinions >Senior Curmudgeon | expressed here DO represent >Cary Consulting Services, Newark, CA | those of the management of >ajlcary@ix.netcom.com | Cary Consulting Services ______________

You can obtain them from the TS area on the SI web site (www.sas.com). Also, you can create a SAS dataset from Access (or any other ODBC compliant app).

I haven't tried it yet, but I was thinking that you might be able to write a Windows batch script that would let you read and write SAS datasets to other ODBC apps from inside a SAS app (at least transparently). Something like selecting an option in an AF app which would close SAS, run a background process in, say Access, that would read or write a SAS dataset, then close the SAS ODBC server and re-start a SAS session and take you back to where you started?

Anyone ambitious enough to try it? I don't have the time or need right now.

Clark Roberts Decision Analytics, A SAS Institute Quality Partner(tm) e-Mail dacmr@interramp.com or 76547.1575@compuserve.com Voice/FAX/Message: (619) 565-9998 Pager: (619) 975-0758 _____________________________________________

SAS and SAS Institute Quality Partner are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ______________________________________________