| 82D226 for Windows |
| Released: Feb 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-006004 |
"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2 |
82D203 |
| SN-005708 |
ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state |
82D203 |
| SN-006276 |
New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo |
82D203 |
| SN-005997 |
Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected. |
82D203 |
| SN-005996 |
Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations |
82D203 |
| SN-005330 |
PROC APPEND to SQL Server using BCP option will insert data incorrectly |
82D203 |
| SN-004053 |
CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver |
82D203 |
| SN-006323 |
Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest |
82D204 |
| SN-006293 |
Read Isolation Level defaults to CR when using SAS/Access Interface toDB2 |
82D203 |
| SN-006312 |
CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows |
82D208 |
| SN-007694 |
NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows |
82D210 |
| SN-008603 |
"No data found" error occurs when trying to update or delete from a DB2table with SQL |
82D216 |
| SN-009478 |
SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table |
82D220 |
| SN-009773 |
Incorrect data when KEEP= contains a field with a binary data type |
82D220 |
| SN-009914 |
/UNIQUE option does not work with ODBC engine for character typedvariables |
82D220 |
| SN-012061 |
"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220 |
82D222 |
| SN-013571 |
Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1 |
82D225 |
| SN-013504 |
SQL3061N received bulkloading to a DB2 table in a DBCS database |
82D225 |
| SN-013980 |
DB2 bulk loader does not run with ALLOW READ ACCESS enabled |
82D226 |
| SN-008941 |
Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2 |
82D226 |
| Install Instructions: 82D226wn.txt |
| Download: 82D226 for Windows (File Size: 1.5M) |
| ATTENTION: To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied. |
| 82OD09 for Windows |
| Released: Feb 2005 |
| Issue(s) Addressed: | Introduced: |
| SN-006004 |
"ERROR: CLI open cursor error: [IBM][CLI Driver] CLI0125E Functionsequence error" issued when using SAS/ACCESS Interface to DB2 |
82OD01 |
| SN-005708 |
ERROR: SQL0514N The cursor "SQLCURCS297" is not in prepared state |
82OD01 |
| SN-006276 |
New special queries added for ODBC and DB2: SQLDataSources and SQLDBMSInfo |
82OD02 |
| SN-005997 |
Access AS400 data using Access Interface to ODBC can causeERROR:[merant][ODBC driver][DB2/400] Keyword FOR not expected. |
82OD01 |
| SN-005996 |
Access Interface to ODBC when accessing MSAccess data may causedata to be overwritten if using APPEND operations |
82OD01 |
| SN-005330 |
PROC APPEND to SQL Server using BCP option will insert data incorrectly |
82OD01 |
| SN-004053 |
CLI ODBC driver error occurs when using SAS/ACCESS Interface to ODBC toaccess LANDMARK DBMS, through LANDMARK ODBC driver |
82OD01 |
| SN-006323 |
Unable to get a single connection when using CONNECTION=GLOBALREAD asdocumentation would suggest |
82OD02 |
| SN-006293 |
Read Isolation Level defaults to CR when using SAS/Access Interface toDB2 |
82OD02 |
| SN-006312 |
CLI prepare error using NEON ODBC Driver to access DB2 on MVS withAccess to ODBC on Windows |
82OD03 |
| SN-007694 |
NonStop Tandem LARGEINT columns causes problems with Access to ODBC V8.2on Windows |
82OD04 |
| SN-008603 |
"No data found" error occurs when trying to update or delete from a DB2table with SQL |
82OD05 |
| SN-009478 |
SAS/Access to ODBC accessing Sql Server 2000 generates errors whencreating a temporary table |
82OD06 |
| SN-009773 |
Incorrect data when KEEP= contains a field with a binary data type |
82OD06 |
| SN-009914 |
/UNIQUE option does not work with ODBC engine for character typedvariables |
82OD06 |
| SN-012061 |
"ERROR: No matching observation was found in MASTER data set" is issuedafter applying HOTFIX 82D220 |
82OD07 |
| SN-013571 |
Bus Error accessing DBMS table via SAS/ACCESS to ODBC with rowset_size>1 |
82OD08 |
| SN-013504 |
SQL3061N received bulkloading to a DB2 table in a DBCS database |
82OD08 |
| SN-013980 |
DB2 bulk loader does not run with ALLOW READ ACCESS enabled |
82OD09 |
| SN-008941 |
Segmentation violation when specifying DBCOMMIT= on the LIBNAMEstatement for DB2 |
82OD09 |
| Install Instructions: 82OD09wn.txt |
| Download: 82OD09 for Windows (File Size: 1.5M) |
| ATTENTION: To complete the installation of this hot fix on Windows platforms, you must also download and install hot fix 82BC07 for Windows. This hot fix will NOT be fully functional without 82BC07 applied. |
| 82OL05 for Windows |
| Released: Aug 2003 |
| Issue(s) Addressed: | Introduced: |
| SN-004249 |
PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file |
82OL01 |
| SN-005811 |
Syntax error when using WGDB option with PROC IMPORT procedure |
82OL01 |
| SN-005812 |
PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine |
82OL01 |
| SN-004195 |
PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly |
82OL01 |
| SN-005506 |
Importing from Excel 97 or 2000 where the sheet name contains an &fails. |
82OL01 |
| SN-006001 |
Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared' |
82OL01 |
| SN-000494 |
Can SAS access Microsoft SQL Server OLAP cubes? |
82OL01 |
| SN-007399 |
ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed |
82OL01 |
| SN-006709 |
PROC IMPORT of Excel 2000 data containing double byte characters aretruncated in SAS |
82OL02 |
| SN-007477 |
Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390 |
82OL03 |
| SN-007806 |
Accessing OLAP cube that contains a currency type will return $0 |
82OL04 |
| SN-005809 |
ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table |
82OL05 |
| SN-010553 |
Unable to list tables or retrieve data using the Ihistorian OLE DBprovider |
82OL05 |
| Install Instructions: 82OL05wn.txt |
| Download: 82OL05 for Windows (File Size: 1.4M) |
| 82PF05 for Windows |
| Released: Aug 2003 |
| Issue(s) Addressed: | Introduced: |
| SN-004249 |
PROC EXPORT of a numeric variable causes missing data in MSAccess2000/XP file |
82PF01 |
| SN-005811 |
Syntax error when using WGDB option with PROC IMPORT procedure |
82PF01 |
| SN-005812 |
PROC IMPORT fails when importing Microsoft files when MDAC 2.70 isinstalled on the machine |
82PF01 |
| SN-004195 |
PROC IMPORT is not setting the SYSLAST and SYSDSN Macros Correctly |
82PF01 |
| SN-005506 |
Importing from Excel 97 or 2000 where the sheet name contains an &fails. |
82PF01 |
| SN-006001 |
Access Interface to OLEDB will fail when attempting to call a storedprocedure with 'command was not prepared' |
82PF01 |
| SN-000494 |
Can SAS access Microsoft SQL Server OLAP cubes? |
82PF01 |
| SN-007399 |
ALERT - Version 8 import procedure might hang after SAS 9 Early AdopterRelease installed |
82PF01 |
| SN-006709 |
PROC IMPORT of Excel 2000 data containing double byte characters aretruncated in SAS |
82PF02 |
| SN-007477 |
Error using Access to OLEDB w/MS V5 DB2OLEDB Provider to access data onOS390 |
82PF03 |
| SN-007806 |
Accessing OLAP cube that contains a currency type will return $0 |
82PF04 |
| SN-005809 |
ERROR: Problem removing original table, when using PROC EXPORT to createan MSACCESS table |
82PF05 |
| SN-010553 |
Unable to list tables or retrieve data using the Ihistorian OLE DBprovider |
82PF05 |
| Install Instructions: 82PF05wn.txt |
| Download: 82PF05 for Windows (File Size: 1.4M) |
| 82BW03 for Windows |
| Released: Oct 2003 |
| Issue(s) Addressed: | Introduced: |
| SN-006764 |
Runtime error when extracting or displaying InfoCube with 0DATEattribute from InfoObject |
82BW01 |
| SN-006766 |
Cannot extract InfoCubes from SAS/ACCESS to SAP BW which have compoundcharacteristics where reference character of compound in SID table doesnot match InfoObject name |
82BW01 |
| SN-006765 |
SQL star view requires excessive space for temporary files in SAS/ACCESSto SAP BW |
82BW01 |
| SN-007682 |
Error creating formats for class variables during InfoCube dataextraction within SAS/ACCESS Interface to SAP BW |
82BW02 |
| SN-007675 |
Full extraction versus change data capture for InfoCubes and ODS inSAS/ACCESS Interface to SAP BW |
82BW02 |
| SN-007719 |
SAS/ACCESS Interface to SAP BW extraction does not recognize certainerror conditions |
82BW02 |
| SN-007674 |
Metadata extractions with FIELDS and TABLES selected from SAS/ACCESSInterface to SAP BW returns metadata about non-relevant tables |
82BW02 |
| SN-010160 |
Extractions of InfoCubes or ODS tables within SAS/ACCESS Interface toSAP BW using remote host metadata fails |
82BW03 |
| SN-008892 |
Misleading error message written when extracting ODS tables that containInfoObjects with compound keys from SAS/ACCESS Interface to SAP BW |
82BW03 |
| SN-010159 |
Change Data Capture feature in SAS/ACCESS Interface to SAP BW mayproduce incorrect InfoCube data for compressed InfoCubes in SAP BW |
82BW03 |
| SN-010158 |
Format names created for infocubes in SAS/ACCESS to SAP BW are notdescriptive |
82BW03 |
| Install Instructions: 82BW03wn.txt |
| Download: 82BW03 for Windows (File Size: 1.5M) |
| ATTENTION: To complete the installation of this hot fix, you must also download and install hot fix 82R302 for your operating system. Customers running in a DBCS environment should download 82R302. This hot fix will NOT be fully functional without both 82BW02 and 82R302 applied. |
| 82SB12 for Windows |
| Released: Mar 2008 |
| Issue(s) Addressed: | Introduced: |
| SN-004321 |
Unable to execute multiple SELECT statements with Access to Sybase inVersion 7 and Version 8 of the SAS System |
82SB01 |
| SN-005897 |
BULKLOAD of DOLLAR 12.2 format using SAS/ACCESS Interface to SYBASEproduces an OVERFLOW error |
82SB01 |
| SN-005909 |
Unable to append to a SYBASE table with BULKCOPY if an identity columnexists on the table |
82SB01 |
| SN-006327 |
SQL Pass-Through to Sybase EXECUTE statement allows only one statement |
82SB02 |
| SN-006335 |
Using PROC DBLOAD APPEND with BULKCOPY may cause data corruption |
82SB02 |
| SN-008355 |
PROC DBLOAD password is not X'd-out in the SAS log when using SAS/ACCESSInterface to Sybase |
82SB04 |
| SN-008473 |
"Error in results set for update" when updating a Sybase view with DATAstep MODIFY |
82SB04 |
| SN-008967 |
SAS/ACCESS Interface to Sybase incorrectly reads the Sybase value'JUN 21 2001 2:03:46:793AM' and generates a warning message |
82SB05 |
| SN-010317 |
Access to Sybase V8.2 is not honoring the database= option for updates |
82SB08 |
| SN-010867 |
Unable to update a Sybase table with an Identity field with SAS V8.2 |
82SB09 |
| SN-012997 |
With SAS 8.2 ACCESS TO SYBASE, Notes, warning or errors are not beingissued when attempting to insertinto a Sybase table with triggers using RAISERROR with PROC APPEND |
82SB10 |
| SN-001373 |
ALERT - SAS/ACCESS Version 6 incompatibility issues with SAS Version 7 andVersion 8 |
82SB10 |
| SN-010795 |
Wrong Sybase table accessed when using the SCHEMA LIBNAME option |
82SB10 |
| SN-015017 |
Segmentation Violation error issued intermittently when accessing aSybase server that is not available |
82SB12 |
| Install Instructions: 82SB12wn.txt |
| Download: 82SB12 for Windows (File Size: 1.9M) |
| 82BB12 for Windows |
| Released: Nov 2002 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| Issue(s) Addressed: | Introduced: |
| SN-004619 |
Risk Dimensions documentation will not display after SAS System Helphas been invoked |
82BA32 |
| SN-005042 |
Margin settings are ignored in Release 8.2. |
82BA32 |
| SN-005201 |
Read-access violation submitting a simple data step on Windows ME |
82BA32 |
| SN-005938 |
The SAS system abends after you select File from the menu bar |
82BA56 |
| SN-004882 |
FIND and REPEAT FIND (RFIND) keys do not work in the Enhanced Editor inRelease 8.2 |
82BA56 |
| SN-007046 |
ALERT - Enterprise Guide may crash when using RTF result format type |
82BA74 |
| SN-006943 |
ALERT - Combo Box may not display blank value using Dropdown List |
82BA74 |
| SN-007007 |
Abnormal SAS termination entering a long string in a Text Pad Control |
82BA74 |
| SN-007766 |
ALERT - When opening SAS System Help 8.2, browser opens and "The page cannot befound" error message appears |
82BB04 |
| SN-008335 |
Scrolling the wheel of an Intelli Mouse while the END command is issuedcrashes SAS |
82BB12 |
| SN-008755 |
Webhound child processes may hang during the reporting phase |
82BB12 |
| Install Instructions: 82BB12wn.txt |
| Download: 82BB12 for Windows (File Size: 2.3M) |
| 82BB46 for Windows |
| Released: Aug 2003 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| Issue(s) Addressed: | Introduced: |
| SN-005210 |
ALERT - LINE statement may display incorrect data with COMPUTE BEFORE and theFLOW option |
82BA36 |
| SN-005223 |
BREAK statement and GROUP under an ACROSS may cause an error |
82BA36 |
| SN-005211 |
ALERT - GROUP values under ACROSS may be missing if BREAK/COMPUTE AFTER variableis requested |
82BA36 |
| SN-005767 |
ALERT - Nested ACROSS variables may result in system specific errors |
82BA36 |
| SN-005770 |
ALERT - Row variable values may be printed under wrong variable column |
82BA36 |
| SN-005766 |
ALERT - Rows of data may be missing from output with multiple ACROSS variablesin PROC REPORT |
82BA36 |
| SN-007784 |
ALERT - PROC REPORT quantile values may be incorrect |
82BA98 |
| SN-007785 |
ALERT - ACROSS values may be missing in the REPORT WINDOW of PROC REPORT |
82BA98 |
| SN-007786 |
BY statement in PROC REPORT may cause memory problems |
82BA98 |
| SN-007888 |
ALERT - All but the first column under an ACROSS variable may contain missingvalues |
82BA98 |
| SN-005776 |
CALL DEFINE specified in COMPUTE block may produce an abend |
82BA98 |
| SN-009218 |
ALERT - Data missing when ANALYSIS variable is requested over multiple ACROSSvariables |
82BB33 |
| SN-009829 |
PROC REPORT _PAGE_ location LINE statements are missing when onlysummary rows are printed on a page |
82BB46 |
| SN-010063 |
PROC REPORT option NOCOMPLETECOLS may apply only to last variable listedunder a nested ACROSS |
82BB46 |
| SN-010051 |
Label for OTHER format range may display in RBREAK summary line |
82BB46 |
| SN-010380 |
The FLOW option on a DEFINE statement may generate garbage characters |
82BB46 |
| Install Instructions: 82BB46wn.txt |
| Download: 82BB46 for Windows (File Size: 1.6M) |
| 82BB84 for Windows |
| Released: Aug 2004 |
| This Hot Fix is included in Hot Fix Bundle 82BX09. |
| Issue(s) Addressed: | Introduced: |
| SN-004574 |
Spanned headers in PROC REPORT may cause incorrect cellwidth when usingODS |
82BA10 |
| SN-004501 |
PROC TABULATE repeats statistics in all ODS destinations except listingand output data sets |
82BA10 |
| SN-004756 |
ODS RTF and ODS PRINTER may take a long time to process |
82BA10 |
| SN-005256 |
Column headers may wrap incorrectly when generating output with the ODSRTF destination |
82BA10 |
| SN-005261 |
ALERT - The CHARSET= and ENCODING= ODS options are ignored by the HTML and XMLdestinations |
82BA10 |
| SN-005850 |
DBCS characters may not display properly when using ODS RTF |
82BA51 |
| SN-005851 |
Certain DBCS characters prevent RTF files from being opened by MicrosoftWord |
82BA51 |
| SN-005425 |
Invalid files generated for ODS printer destinations in Asian encodings |
82BA42 |
| SN-005950 |
ODS PDF does not render Latin1 (ISO 8859-1) encoding correctly |
82BA54 |
| SN-005951 |
ODS PDF and RTF can not produce double-byte encoded output |
82BA54 |
| SN-005949 |
ODS PDF will only use Times, Helvetica, and Courier as default font |
82BA54 |
| SN-005596 |
Output data set may not be generated when using the ODS OUTPUT statement |
82BA44 |
| SN-007190 |
Incorrect Japanese character appears in ODS RTF output on DBCS systems |
82BA83 |
| SN-007191 |
Generating ODS/RTF output using the ESCAPECHAR option causes errors onDBCS systems |
82BA83 |
| SN-009281 |
The OVERPRINT system option does not work correctly with the ODS PRINTERand PDF destinations |
82BB37 |
| SN-010318 |
User-defined format can not be updated when applied to a variablecreated with ODS OUTPUT |
82BB61 |
| SN-010411 |
ALERT - Customized template may cause observations to not appear in ODS PRINTERoutput |
82BB61 |
| SN-005994 |
Using a PREIMAGE= specification and STARTPAGE= with ODS PRINTER causeserrors |
82BB61 |
| SN-010821 |
ODS RTF incorrectly displays some symbol characters defined from DBCSsystems |
82BB61 |
| SN-009366 |
ODS PRINTER does not close registry keys properly |
82BB84 |
| Install Instructions: 82BB84wn.txt |
| Download: 82BB84 for Windows (File Size: 2.8M) |
| ATTENTION: If you downloaded hot fix 82BB97 before August 4, 2004, you must back off 82BB97 and re-install 82BB84. 82BB97 is currently NOT available for DBCS supported installations. |
