LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (November 2004, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 23 Nov 2004 07:12:20 -0500
Reply-To:     JumboShrimps <Jumbo_shrimps@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         JumboShrimps <Jumbo_shrimps@HOTMAIL.COM>
Organization: Posted via Supernews, http://www.supernews.com
Subject:      Linking Access 2000 to SAS 8.1

ODBC -call failed [SAS][SAS ODBC Driver][SAS Server][178-TCP method failed rc= -1019 (Timeout waiting for the SAS server..... [Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr failed IM006 0....etc.

Set up the latest SAS ODBC drivers using article TS626 , and the latest MDAC from Microsoft on a Win2k platform for PC SAS 8.1 running on the local C:\ drive. Did make a server entry in the Microsoft services file per the article, but how would SAS know about that? It's an arbitrary tcp number anyway.

Also, TS626 references a specific file name in the library set up (has to be USER for Access 2000). While I do have a USER library, there is no file named USER in the SAS files directory I'm pointing to (or anywhere else for that matter). Again, that could be the problem.... .


Back to: Top of message | Previous page | Main SAS-L page