| E67024 for Windows |
| SAS Add-in for Microsoft Office 4.305 |
| Issue(s) Addressed: | Introduced: |
| 13604 | WHERE clause might be too long and cause syntax errors in SAS® Enterprise Guide |
E67014 |
| 42623 | Data items with the same name from different tables might be switched when modifying the Import Data task in SAS® Enterprise Guide® |
E67014 |
| 42693 | The SAS® Add-in for Microsoft Office generates an error when you invoke Microsoft Excel from a Web application |
E67014 |
| 42975 | Scheduled projects that contain a condition might stop responding in SAS® Enterprise Guide® |
E67014 |
| 43047 | "File or Directory" prompt type does not work when the workspace server is on the same machine as SAS Enterprise Guide |
E67014 |
| 43331 | After installing SAS® Add-in for Microsoft Office, problems occur when multiple user accounts open Microsoft Office |
E67014 |
| 43696 | Length of character computed column from SAS® Information Map might be truncated to 32 |
E67014 |
| 43737 | SAS® Stored Process prompt list is not sorted by unformatted value if SAS® Enterprise Guide® created the prompt |
E67014 |
| 43796 | Plot with one-step-ahead predictions and future forecasts is not available in ARIMA task in SAS® Enterprise Guide 4.3 |
E67014 |
| 43888 | Prompt list might not be sorted correctly in SAS® Enterprise Guide® |
E67014 |
| 44352 | Code generated by the Query Builder might result in syntax errors due to incorrect parsing |
E67014 |
| 44629 | SAS® Enterprise Guide® might encounter a problem connecting to a SAS application server in a SAS grid environment |
E67014 |
| 46013 | Formatting might be removed when sending results from SAS® Enterprise Guide® to Microsoft Excel |
E67014 |
| 46087 | Opening a protected Microsoft Word document with Microsoft Office 2010 might display an exception in the SAS® Add-In for Microsoft Office |
E67014 |
| 43807 | Conditional highlighting for negative values might not be applied to reports opened in SAS® Enterprise Guide® or the SAS® Add-In for Microsoft Office |
E67020 |
| 43878 | An Application Error might occur when using the Logistic Regression task in SAS® Enterprise Guide® |
E67020 |
| 43884 | Data sets in migrated SAS® Enterprise Guide® projects might have incorrect creation and modification dates |
E67020 |
| 43948 | A filter string that contains the IN operator might fail after migration from the SAS® Add-In 2.1 for Microsoft Office |
E67020 |
| 44226 | Reports that contain empty tables might not correctly display in SAS® Enterprise Guide® and the SAS® Add-In for Microsoft Office |
E67020 |
| 44391 | Disabled row numbers reappear after migrating workbook to the SAS® Add-In 4.3 for Microsoft Office |
E67020 |
| 44503 | Unable to migrate or refresh a worksheet with a simple filter when using the SAS® Add-In for Microsoft Office |
E67020 |
| 44563 | Formula no longer works in Microsoft Excel after migrating a worksheet from the SAS® Add-In 2.1 for Microsoft Office to version 4.3 |
E67020 |
| 44580 | "Unable to render the data view" when adding a filter to a table in Microsoft Excel using the SAS® Add-In for Microsoft Office |
E67020 |
| 44581 | Table formatting might be lost after refreshing a table that has been migrated from the SAS® Add-In 2.1 for Microsoft Office to version 4.3 |
E67020 |
| 44856 | "Cannot open this item" might appear when opening e-mail in Microsoft Outlook when the SAS® Add-In for Microsoft Office is enabled |
E67020 |
| 44933 | Row numbers display in output data after migrating the workbook to the SAS® Add-In 4.3 for Microsoft Office |
E67020 |
| 45695 | Using an analysis variable with all missing values prevents the summary statistics task from running |
E67020 |
| 44984 | Graphs generated by SAS tasks in the SAS® Add-in for Microsoft Office might generate incorrect results when input data is filtered in Microsoft Excel |
E67022 |
| 45434 | Dashboards created with SAS® BI Dashboard 4.31 cannot be opened in Microsoft Outlook using the SAS® Add-In 4.3 for Microsoft Office |
E67022 |
| 45435 | Task template error might appear when refreshing SAS® Add-In for Microsoft Office content |
E67022 |
| 46428 | "Index was outside the bounds of the array" appears when viewing details for a Microsoft Excel PivotTable that contains more than 256 columns |
E67024 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
| E67026 for Windows |
| SAS Add-in for Microsoft Office 4.305 |
| Issue(s) Addressed: | Introduced: |
| 41548 | In SAS Enterprise Guide® 4.3, the Stored Process Wizard will not allow the Source File Path on z/OS® to use an hfs file |
E67016 |
| 43549 | Tasks will not run properly in Hebrew due to encoding issue with footnotes |
E67016 |
| 43696 | Length of character computed column from SAS® Information Map might be truncated to 32 |
E67016 |
| 43796 | Plot with one-step-ahead predictions and future forecasts is not available in ARIMA task in SAS® Enterprise Guide 4.3 |
E67016 |
| 45008 | Missing OK and Cancel buttons when attempting to filter and sort an information map in specific languages using the SAS® Add-In for Microsoft Office |
E67023 |
| 45250 | DBCS functions are not listed on "New Computed Column" Window |
E67023 |
| 45916 | "Show Member Property" on an OLAP cube produces an error in SAS® Enterprise Guide 4.305 and SAS® Add-in for Microsoft Office 4.305 |
E67025 |
| 46279 | "Options" selections in Stored Process Wizard is incomplete in Polish environment |
E67026 |
| NOTE: This hot fix is applicable to systems with one or more of the following languages installed:
Chinese (Simplified), Chinese Traditional (Taiwan), Chinese Traditional (Hong Kong SAR), Danish, Dutch, French, German, Hebrew, Italian, Japanese, Korean, Polish, Russian, Spanish, Swedish, Turkish |
| NOTE: You must also install hot fix E67024 to fully implement fixes in this hot fix. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes