Instructions for installing the patch for
the Warehouse Builder client component

Service Level 3.01.140
December 2001

Please read and print these instructions before installing the patch!

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

English (6.33 MB)
French (4.02 MB)
German (4.39 MB)
Spanish (3.96 MB

Patch Installation Instructions

1. Download the patch for your language
2. Copy the patch to your STRATEGY \Bin directory. This is the folder that contains the executable files such as VISTA.EXE. (NOTE: Do not copy this file to your Backup folder)
3. Rename or delete the existing Backup folder that contains previous ShowCase patch applications
4. Double-click on the patch executable

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 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 without deleting the Backup directory, the BACKUP directory will contain multiple copies 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 latest unpatch.bak (or unpatch.bat if you already renamed it) file and the files listed in its text.

Summary of problems fixed
This patch will resolve the following:

Products Affected: Warehouse Builder

• BETWEEN predicate with 3 variables will no longer GPF, when the prompts are left empty. (F7777)
• Query will no longer gpf on condition using BETWEEN with a days(date) prompt. (F5353)
• Resolved a problem where function LEFT failed when an expression was used as the length argument. (F7322)
• Non-join conditions will be correctly moved from the 2.5 Join dialog to the 3.0 Condition dialog when 2.5 queries are opened in 3.0. (F6328)
• 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. (F6705)
• Joins involving quoted column names can be edited from the Table Dialog. (F6901)
• Alias names will be quoted if they contain variant characters. (F6866)
• Global Variables that have the prompt attributes check box marked for "Skip Prompt if Variable has Value" will no longer prompt on subsequent queries, once the value has been set. (F5474)
• 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. (F6705)
• Will support an expression with AND OR NOT in the If or Else If parts of the If-Then-Else Assistant. "(F3743)
• The conditions involving AND and OR will not be lost on converting to join conditions. "(F5816)
• "Column not found in datasource" will not be issued when importing AS/400 query objects that contains lower case letters."(F5971)
• 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)
• Will support an expression with AND OR NOT in the If or Else If parts of the If-Then-Else Assistant. "(F3743)
• 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)
• 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)
• The correct default data type will be displayed in the "Save As Data" dialog for Text. "(F4124)
• 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)
• Prompted variables will keep the apostrophes when default to current variable is selected and correct data will be retrieved. "(F4686)
• Japanese characters will be displayed in the splash screen. "(F4996)
• DBCS characters can now be used in both the Names and Descriptions on the columns dialog. "(F5003)
• 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)
• The quoted '(' and ',' in case statements should not be changed now and correct results should be retrieved. " (F4500)
• Make the version information consistent between the Splash and the About dialog boxes. (F4067)
• Target column descriptions and headings will now be retrieved when creating a new definition against an existing Target Table. In addition, existing data in the Target Table will NOT be deleted when "No" is the response to the "Replace existing table definition and data. (F6970)
• 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)
• No longer receive a GPF due to the font setting of the sample data grid on Japanese and Chinese versions of Windows. " (F4363)
• 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)
• 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)
• 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)

• Breakgroups/summary information will be displayed when using Data Reference option "Query Viewer Data" for Lotus 123. (F6454)
• 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)
• Lotus Addins will return data for more than one row and will no longer return NA when valid data is present. "(F5310)
• Lotus Addins will no longer GPF when NULL Values are returned with Numeric Data."(F5496)
• 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)
• Closing of Lotus/Excel after refreshing the contents of a spreadsheet will no longer cause a page fault.. " (F4517)

• The ShowCase addins will no longer gpf(Win95) or produce garbage characters(Win NT) in a prompt cell when refreshing a sheet with multiple variables. (F7578)
• Column headings will be displayed when a linked query returns no data. (F6385)
• 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)
• LinkedAreaName will no longer be reassigned to an added column. "(F4835)
• 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)
• Closing of Lotus/Excel after refreshing the contents of a spreadsheet will no longer cause a page fault.. " (F4517)
• 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)

Back to Patch Description