Providing software solutions since 1976
When you use the SAS ODBC driver to access a local SAS server or a remote SAS/SHARE® server, you might see the many SAS map data sets in the selection list of data sets. There are approximately 1,000 data sets, many ...
You can access DBMS library that is defined in SAS Management from third party ODBC application using SAS ODBC driver and SAS/Share.® You access the library as follows: Step 1: Define a DBMS Library First you need to ...
When you try to access a SAS data via the SAS ODBC driver, you might receive the following persistent error: ODBC--call failed. [SAS][SAS ODBC Driver][SAS Server]178 - TCP method failed rc = -1005 (Unable to locate ...
30779 - Suppressing the Getting Started dialog box when you use the SAS ODBC Driver- Usage Note
When you use the SAS ODBC Driver from an application, the Getting Started dialog box displays automatically. To prevent this dialog box from displaying, add the following option to SASV9.CFG file: -notutorialdlg ...
15686 - Where to find the SAS ODBC driver- Usage Note
You can download the SAS 8 and SAS 9 ODBC drivers from the following location and click on the link for the ODBC drivers: http://www.sas.com/apps/demosdownloads/setupintro.jsp The drivers are also included with Base ...
10820 - How to clear the log automatically when running PROC ODBCSERV- Usage Note
When using the SAS ODBC driver with other applications and trying to update or append to SAS data sets, the PROC ODBCSERV window might become full. If you do not want to get prompted and do not care to look at the log ...
15345 - How to specify a SAS datetime constant in a .NET application using the SAS ODBC driver- Usage Note
When querying a SAS datetime value in a .NET application with the SAS ODBC driver, you must use syntax like the following: WHERE DT='01MAY2005:00:00:00'D; instead of: WHERE DT='01MAY2005:00:00:00'DT;
12752 - "Error: PROC ODBCSERV is not permitted to this environment without a SAS/SHARE*NET license" message- Usage Note
Beginning with SAS 9.0, we prohibit PROC ODBCSERV from running on anything but Windows workstations unless SAS/SHARE is licensed. If you try to access SAS data sets from a local ODBC compliance application such as MS ...
13072 - ODBC driver does not work with server that has OPTIONS NETENCRYPT set- Usage Note
If you attempt to connect through ODBC to SAS datasets on a SAS/SHARE server that has the NETENCRYPT system option enabled, the following error message appears: [SAS][SAS ODBC Driver][SAS Server]178 - TCP method ...
7512 - SAS ODBC or SAS Universal ODBC Driver does not appear in ODBC Manager after installation- Usage Note
If after an error-free installation, the SAS ODBC Driver or the SAS Universal ODBC Driver does not appear in the ODBC Administrator/Manager, check the version of MDAC on the pc in which you installed SAS. If the MDAC ...
6446 - How to suppress SASLOG when using SAS ODBC Driver- Usage Note
In order to suppress the SASLOG when using the SAS ODBC Driver, you will need to edit the sasodbc macro in sas\core\sasmacro\sasodbc.sas and add the following 3 lines before the %macro. filename foo dummy; proc ...
10635 - SAS 8 ODBC Driver fails with long dataset name- Usage Note
The SAS 8.0 ODBC driver fails with "error 79-322 expecting a )" when specifying a dataset name that is too long. In the Version 8 (TS0M0) SAS ODBC driver, the SQL code that is built by the driver may be truncated. ...
11354 - How to eliminate GIS Maps data sets from the listing when using SAS ODBC- Usage Note
When using the SAS ODBC driver from other applications to read SAS data sets, you will see GIS Maps data sets along with desired data sets if you have SAS/GIS Maps installed. Having all the GIS MAPS listed can be ...
11208 - "Error: File WORK.MSYSCONF.DATA does not exist" error message appears for query via Jet engine- Usage Note
When an SQL query from a Microsoft JET-engine-supported application (such as MS Access or MS Excel) is sent to a SAS/SHARE server, an error message might appear in the SAS/SHARE server log: When username(n) in " ...
9794 - "Invalid argument value or missing required value" returned when accessing SAS 9 ODBC datasource- Usage Note
When accessing a SAS ODBC datasource, using the SAS 9 ODBC driver configured to access the 8.2 sas.exe, the following error is returned: [SAS][SAS ODBC Driver]Invalid argument value or missing required value(#-1) [ ...
10002 - SQL STATE Errors when using SAS/ODBC drivers to an external client- Usage Note
When you using remote clients to connect to data using SAS ODBC drivers, the following SQL STATE 1000 error message might appear: You must license SAS/INTRNT Software. This message can have one of two causes: 1. ...
8596 - Syntax error when accessing GDG data set from MS Query wizard via ODBC- Usage Note
When you attempt to retrieve data from a SAS Generation Data Group (GDG) data set from a Microsoft Query Wizard for applications such as Excel or MS Access by using the SAS ODBC Driver, you will get a syntax error for ...
6391 - Does SAS/ACCESS provide support for accessing Cold Fusion,a web-based application on Unix platforms?- Usage Note
According to www.coldfusion.com, Cold Fusion is a web application server. Therefore, the web application would be talking to ODBC down to a target datasource. If this is the case, you may want to have SAS be the ODBC ...
6592 - SAS ODBC Driver fails with Microsoft Data Access Components 2.6- Usage Note
When Microsoft Data Access Components (MDAC) level 2.6 is installed on Windows, the SAS ODBC driver fails to work properly. The main observed symptom of this is the following message segment that can occur in several ...
6470 - Error occurred during the move data process -115 when installing SAS ODBC driver under WIN2000- Usage Note
When try to install SAS ODBC driver on WIN2000 and not logged on with Administrator rights, error will occurred error occurred during the move data process -115 Make sure to be logged on with Administrator rights.
4192 - The SAS ODBC driver does not work with Microsoft Project 98 or Microsoft Project 2000.- Usage Note
You cannot import a SAS data set into Microsoft Project and you cannot export a project into SAS data sets. This is because Microsoft Project requires data types that are not supported by the SAS ODBC driver. There are ...
