Warehouse Builder client patch

Please read and print these instructions before installing the patch!

These patches are language specific. Please download the patch for your language only.
 

Patch	Applicable Version
English (4.0 MB)	STRATEGY 3.0 (12/08/99 and later)
French (2.07 MB)	STRATEGY 3.0 (03/06/00)
German (2.16 MB)	STRATEGY 3.0 (03/06/00)
Spanish (2.02 MB)	STRATEGY 3.0 (03/24/00)

Applicable Versions
This patch applies to ShowCase Analyzer, Analyzer for the Web, Excel Add-ins, Query, Report Writer, Scheduled Report Server, Warehouse Builder, Warehouse Manager Client, and Web Servlet version 3.01.000 and later. Apply this patch if you are using one or more of these applications. After the patch is applied, these products will be upgraded to STRATEGY 3.01.060.

Summary of problems fixed
This patch will:

• When selecting 'subset' in the search dialog, the Analyzer application would be minimized."(F4541)

Products Affected: Analyzer
• If row limit was exceeded in a report when using the Grid API function, a message stating that the data was truncated was not displayed. "(F5286)

Products Affected: Analyzer
• When exporting or importing a large group, the PC would run out of memory and never finish. "(F5473)

Products Affected: Analyzer
• Access violation occurs when trying to load a view with verticle banding. "(F5700)

Products Affected: Analyzer
• After migrating a translated version of Strategy from 2.5 to 3.0, you can no longer open data models via Analyzer."(F5741)

Products Affected: Analyzer
• After applying Patch 4 or 5, using the Print Page option caused the following error in Analyzer " Error Reading PrintStatus.Align:Invalid Property value""(F6091)

Products Affected: Analyzer
• Editing LCASE / UCASE functions will not cause the application to hang. "(F5608)

Products Affected: Query
• Deleting a column from the Query viewer will not longer cause an invalid page fault when the query contains a sum function and a JDE UDC column. "(F5977)

Products Affected: Query
• Deleting a column from the Query viewer will not longer cause an invalid page fault when the query contains a sum function and a JDE UDC column. "(F6039)

Products Affected: Query
• UDC/Associative columns in the THEN and ELSE clause of the case statement will return error the error message; "Associative join column not allowed in this context". "(F5085)

Products Affected: SCCOMP
• Will support an expression with AND OR NOT in the If or Else If parts of the If-Then-Else Assistant. "(F3743)

Products Affected: SCCOMP
• The conditions involving AND and OR will not be lost on converting to join conditions. "(F5816)

Products Affected: SCCOMP
• "Column not found in datasource" will not be issued when importing AS/400 query objects that contains lower case letters."(F5971)

Products Affected: SCCOMP

• List index out of bounds error when you click OK in Formatting of List dialog. "(F2078)

Products Affected: Analyzer
• We now get the correct value of the time format from the operating system."(F4892)

Products Affected: Query
• In order to redirect where temporary files get created you need to add the following line in your registry under ShowCase | Query | Options. TemporaryPathName=existing directory you want to set the new location to. By default we still create temporary files in c:\temp. "(F5185)

Products Affected: Query
• Numeric 15 fields will no longer be converted into CHAR 33 when writing results to a dBase (dbf) file. "(F5224)

Products Affected: Query
• Check the status of the prompt dialog, if it's canceled then do not continue with the settings in the result options dialog. "(F5266)

Products Affected: Query
• Changed to not add the international separators a second time when opening the Edit SQL dialog. "(F5304)

Products Affected: Query
• Starting the page break calculations with the first row will give the correct page breaks. "(F5345)

Products Affected: Query
• Lotus 123 will no longer display the #Missing in the columns of the second row, when only one extended data row is being returned. "(F3466)

Products Affected: Query Lotus Add-In
• Lotus Addins will return data for more than one row and will no longer return NA when valid data is present. "(F5310)

Products Affected: Query Lotus Add-In
• Lotus Addins will no longer GPF when NULL Values are returned with Numeric Data."(F5496)

Products Affected: Query Lotus Add-In
• Lotus Addins has a max row limit of 65535. If attempting to retrieve rows greater than 65535, error message will be issued warning that data will be lost. Return the first 65535 rows of data to Lotus. "(F5579)

Products Affected: Query Lotus Add-In
• Will now return the derived field with an international separator. "(F5175)

Products Affected: Report Writer
• Doesn't apply formatting to empty character fields. "(F5385)

Products Affected: Report Writer
• When a scheduled report is copied, in Schedule Report Manager, the user name and password will default to the current user."(F5486)

Products Affected: Scheduled Report Server
• DBCS column names will be allowed, but they will not be used when generating the SQL statement to execute. This also means that Batch Output to Table will not generate DBCS column names since they are based on the name passed in the SQL statement. Also, the user cannot create Data Views with a DBCS NAME or SYSTEM NAME since these are based off the SQL statement.

Japanese Katakana characters will be allowed in the SQL statement as table and column qualifiers. Qualifiers with these characters will be quoted as required by SQL/400. DataViews and Query Batch can use these characters as table and column qualifiers and will behave normally. "(F3655)
Products Affected: SCCOMP
• Will support an expression with AND OR NOT in the If or Else If parts of the If-Then-Else Assistant. "(F3743)

Products Affected: SCCOMP
• Correct information is displayed in condition dialog when regional settings are changed. Also corrected for the columns dialogs and assistants, and since the international separators are added when building the SQL they don't need to be added a second time when entering the SQL statement dialog. "(F4899)

Products Affected: SCCOMP
• When using the SQL function CHAR, Query and Report Writer would display the error message "Function and argument data types do not match" when a String Literal or a Query Date Variable (without anything else in the function) was the argument to the CHAR function. The SQL spec allows Strings, Dates, and Numbers as the argument to the function CHAR. Query and Report Writer will now allow all of these arguments to the CHAR function. "(F5172)

Products Affected: SCCOMP
• Increase the maximum number of rows to 65535 instead of 16384. 65535 is the maximum number of allowed rows for 32 bit Excel. "(F5544)

Products Affected: SCCOMP
• Added ability for ShowCase Data Administrators to control auditing from Warehouse Manager Client."(F4157)

Products Affected: Warehouse Manager Client

• When using a data model in Analyzer, you could not create a list over a dimension unless the field type was a date. Lists over non-date dimensions is now possible. "(F3186)

Products Affected: Analyzer
• Allow the ability to disable printing and/or data export on a per user basis for Analyzer users. "(F4162)

Products Affected: Analyzer
• Occasionally when viewing forms that included buttons that were set on a frame or picture would cause one or more exceptions. You may also experience this problem if your form is larger than what can be displayed in Analyzer and scrollbars are present. Clicking the button when the scrollbar overlapped the frame at times caused an infinite number of exceptions being thrown. " (F4794)

Product(s) affected: Analyzer
• Right click option under the Create Lists function while in the browser, did not enable the following options:

Save Selection as New List
Save Selection as New Sublist
Save Selection Over Existing List "(F4915)
Products Affected: Analyzer
• Using BETWEEN condition between date fields and a Fox Pro driver should work. "(F4742)

Products Affected: Query
• Added ability to save results of scheduled queries and reports to PC files and network shares. Enables publishing to an Xpedio watched folder for automatic publishing. "(F4836)

Products Affected: Query
• Query will no longer issue an invalid page fault when creating a prompt from a column with a space in the alias name. "(F4930)

Products Affected: Query
• Select All Data will no longer issue the application error when using to Cut&Paste into a spreadsheet. "(F5210)

Products Affected: Query
• If Column Definition is greater than 4000 characters, Truncate to 4000 characters. Used to avoid divide by zero GPF in Excel for Windows 95. "(F4678)

Products Affected: Query Excel Add-in
• LinkedAreaName will no longer be reassigned to an added column. "(F4835)

Products Affected: Query Excel Add-in
• Excel will use either "column name" or "column description" , depending on the Options setting in Query. Excel won't use the column definition anymore for a column heading. "(F4987)

Products Affected: Query Excel Add-in
• Resolved a problem where Report Writer would fail when adding a Report Group over a large result column such as a large CASE statement. The fix requires that "Show Names First, Descriptions Second" be checked in the "Tools | Options | Display" dialog. "(F3576)

Products Affected: Report Writer
• The correct default data type will be displayed in the "Save As Data" dialog for Text. "(F4124)

Products Affected: Query, Report Writer and Warehouse Builder
• 1. Fixed retrieving distinct table references from the from clause aliases. We were initially retrieving duplicate table references when more than one alias had the same table reference. Cause problems with change link.

2. During change link we were only considering the first subquery to retrieve the invalid tables - unions and multiple subqueries would cause problems. Added a loop to look at all subqueries.
3. Make linkage mapkey was not generating the correct key - causing memory leaks as we had the same key being generated and we made multiple new objects and did not delete all of them. Now creating distinct linkage keys by getting the owner and table name if the system names are empty. "(F4511)
Products Affected: Query, Report Writer and Warehouse Builder
• Prompted variables will keep the apostrophes when default to current variable is selected and correct data will be retrieved. "(F4686)

Products Affected: Query, Report Writer and Warehouse Builder
• Japanese characters will be displayed in the splash screen. "(F4996)

Products Affected: Query, Report Writer and Warehouse Builder
• DBCS characters can now be used in both the Names and Descriptions on the columns dialog. "(F5003)

Products Affected: Query, Report Writer and Warehouse Builder

• Resolved a problem when errors were returned when importing a .dbq into Report Writer. "(F4658)

Products Affected: Report Writer
• Exception "List index out of bounds" occurred in application, when trying to load a view. The error comes from a calculation saved in the view definition, that has a leading or trailing space in the name. " (F4375)

Product(s) affected: Analyzer
• Logic was introduced to determine the number of columns to be written. " (F3687)

Product(s) affected: Query
• Empty cells will no longer show the word "NULL". " (F4092)

Product(s) affected: Query
• Incorrect numbers of tab characters in a string was used to display the string, which caused GPFs. The codes have been changed to fix the problem. " (F4356)

Product(s) affected: Query
• Closing of Lotus/Excel after refreshing the contents of a spreadsheet will no longer cause a page fault.. " (F4517)

Product(s) affected: Query Lotus Add-In
• The error when installing using a UNC naming convention has been fixed. The problem existed when trying to parse the macro path to determine if it was valid. The parsing didn't account for UNC naming conventions and errors occurred.

If the GPF still occurs after applying the patch then delete the RSmith32.GMC (global macro file) and retry. Before the fix RW GPF'd while trying to open the RSmith32.GMC which was pointed to as a UNC path. Because RW gpf'd the RSmith32.GMC file didn't get closed properly so it's corrupted. " (F1938)
Product(s) affected: Report Writer
• Changed the application of the default edit mask. It now changes the international decimal separator to what is in regional settings. " (F4332)

Product(s) affected: Report Writer
• Added a check to use the windows regional settings system date format to resolve a problem whereby in a German Query/German Windows environment date conditions involving 01/01/0001 could not be added. " (F4633)

Product(s) affected: Report Writer, Query and Warehouse Builder
• The quoted '(' and ',' in case statements should not be changed now and correct results should be retrieved. " (F4500)

Product(s) affected: Report Writer, Query and Warehouse Builder
• Warehouse Builder was not updating the sequence of a set of definitions. This is because our routine to perform the updates was failing. The failure occurred because the information that details the sequence of the definitions was missing. " (F4202)

Product(s) affected: Warehouse Builder
• The sequence associated with a definition was not being added. The order was taken from the order that appeared in the list of available definitions. Added the correct sequence value to the definition when the customer selects OK on the Add Definitions to Set dialog. " (F4223)

Product(s) affected: Warehouse Builder
• No longer receive a GPF due to the font setting of the sample data grid on Japanese and Chinese versions of Windows. " (F4363)

Product(s) affected: Warehouse Builder
• Removed logic to hide password options on IBM install for LPP. " (F4188)

Product(s) affected: Warehouse Manager Client

• Eliminate the following error message, which occurs while trying to change types when both form views and spreadsheet or pinboard views were loaded: "The form view has no data display, so this option is invalid." (F2920)

Product(s) affected: Analyzer
• Allow the export function to export all views in a group. (F3976)

Product(s) Affected: Analyzer
• Fix the automated build for Analyzer 3.0. (F4221)

Product(s) Affected: Analyzer
• Make the version information consistent between the Splash and the About dialog boxes. (F4067)

Product(s) Affected: Analyzer and Report Writer
• Resolved a problem that resulted in no statistics when scheduling a query or report, even though users would see an error message of "[30] Message: MSG_ID_EXECUTION INSTANCE ERROR Error occurred executing the scheduled item. Please check statistics." (F3975)

Product(s) Affected: Query
• Change edit mask processing to display the correct values of numeric or decimal data. Previously, edit masks applied to numeric or decimal data (but not real, double, or float) might have resulted in incorrect output due to rounding and/or truncation. (F1262)

Product(s) Affected: Query
• Add a file extension (.txt) to the table name. Previously, an error message "Table not found in Datasource" appeared when accessing a table via the MS ODBC txt driver. (F4052)

Product(s) Affected: Query
• Return a value of #N/A for a summary field in Excel, if a linked query returns 0 rows and a NULL value for the summary field. (F4090)

Product(s) Affected: Query Excel Add-ins
• Fix the following issue: Report Writer and Query use DDE to pass information back and forth. The Query .dbq file is one of these pieces of information. Windows95 and Windows98 have a memory limitation for a DDE buffer that cannot exceed 64K bytes. If the .dbq file size grew to larger than 64K, then only a partial .dbq was passed between the two applications, resulting in an invalid .dbq. The fix is implemented to not use a DDE buffer to pass the .dbq; instead, we use shared memory, which can grow larger than 64K. (F4222)

Product(s) Affected: Report Writer
• Add a string to display a message that the user is restricted to print according to the administrator setting. (F3515)

Product(s) Affected: Report Writer
• Add a file attribute so that the file can be opened correctly. (F4168)

Product(s) Affected: Report Writer
• Track all changes to the Control Tables related to a Definition object and updates this information regardless of whether the Table itself is being created or altered. (F3751)

Product(s) Affected: Warehouse Builder
• Change the method to save definition changes. We now use the same code as File > Save to make sure that all Control Table entries get changed on an update of Target Library or Table. (F4011)

Product(s) Affected: Warehouse Builder
• Eliminate problems with auditing showing negative elapsed times. All timestamps are now retrieved from the AS/400 from where the auditing is run. (F2413)

Product(s) Affected: Warehouse Manager Client
• Fix formatting problems when there is an alias on Measures dimension. (F4018)

Product(s) Affected: Warehouse Manager Client
• Add ability for ShowCase Data Administrators to control auditing from Warehouse Manager Client. (F4157)

Product(s) Affected: Warehouse Manager Client

Patch Installation Instructions
The first time you apply a patch to a ShowCase feature, you must download the patchw32.dll file. This file contains the core functionality for the patch program used by the PTF. We recommend that the patchw32.dll be copied to the Windows System directory and be retained there for future use.

1. Download the Patch (4.0 MB)
2. Copy the patch to your STRATEGY \Bin directory. This is the file that contains the executable files such as VISTA.EXE. (NOTE: Do not copy this file to your Backup folder)
3. Double-click on C301060.exe.

The patch program runs and automatically modifies, adds, renames, or deletes files as necessary to complete the patch.

The original file is saved in the BACKUP directory, which is automatically created on the drive from which the patch is run.

Undoing the Patch
If you want or need to get back to the original files (before the patch was applied), you will find them in the BACKUP directory, which is located on the drive that the patch is run from. The BACKUP directory contains a file called unpatch.bak. This file is a script file containing the commands necessary to automatically restore the original files. To restore the original files (from any operating system environment):

1. Locate the unpatch.bak
2. Rename the unpatch.bak to unpatch.bat
3. At an MS-DOS prompt, type the path to unpatch.bat (E.g., C:\ProgramFiles\STRATEGY\Desktop\Backup\unpatch.bat) and press Enter.

OR
On the desktop, click Start > Run, and browse for the patch to unpatch.bat. Click OK.

If you apply multiple PTFs over time, the BACKUP directory will contain multiple, consecutively numbered copies (for example, unpatch.bak, unpatch.001, unpatch.002) of unpatch files and the related original files from each backup. You may wish to periodically clean the BACKUP directory to recover disk space. To keep the most recent backup information, keep the unpatch.bak (or unpatch.bat if you already renamed it) file and the files listed in its text.

Back to Patch Description