Kbase 15597: Release Notes for Windows 8.0a02
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Release Notes for Windows 8.0a02
PROGRESS Version 8.0A02 Release Notes
Release: 8.0A02
Ports: MS-Windows
Products: All
Date: March 1996
The following release notes describe the PROGRESS Version 8.0A Issues for
the MS-Windows platform.
WARNING: BEFORE YOU INSTALL Version 8.0A, you MUST migrate any
existing Version 6, Version 7, Version 8.0A1B or 8.0A3B beta local
databases using PROUTIL with the CONV68 or CONV78 qualifier.
For further information see the "PROGRESS Product Update Description."
These release notes describe the following categories of issues.
Database Access Issues
Installation Issue
4GL Issues
International Issues
User Interface Builder Issues
Browse Widget Issues
Translation Manager Issues
Report Builder Issues
DataServer Issues
GUI RESULTS Issue
ODBC Driver Issues
WIN95 Issues
Database Access Issues
The topics in this section describe database access issues.
Cluster Size Wrong in Before Image (.bi) File
Cannot Use Version 8 Data Dictionary for Version 7 Database
Schema Changes
Newkw68 File Added to DLC Dictionary
Cluster Size Wrong in Before Image (.bi) File
The log (.lg) file incorrectly reports the number of 16K clusters
currently configured for the before image (.bi) file. The actual
cluster size would be the number reported in the log file multiplied
by 16.
Cannot Use Version 8 Data Dictionary for Version 7 Database Schema
Changes
Release Note Number: 80AC-20170
The underlying PROGRESS database metaschema for Version 8 differs
from Version 7.
Therefore, you cannot use the Version 8 Data Dictionary to make
changes to Version 7 database
schemas.
Workaround: If you want to edit Version 7 database schema from
within the Version 8 development environment, you must obtain a
copy of the "V8DD7" patch from ProgressTechnical Support.
The V8DD7 patch contains a copy of the Version 7 Data Dictionary
that hasbeen recompiled under Version 8 so that it can execute
within the Version 8 ADE and make changes to remote Version 7
database schemas.
After you install the V8DD7 patch, you have two Data Dictionary
tools under Version 8--one forediting Version 7 schemas (the patch)
and one for editing Version 8 schemas (commercial V8).
You can obtain V8DD7 through any of the following avenues:
Call a Progress sales administrator and order a copy of V8DD7
Download V8DD7 from Progress Software Corporation´s FTP
site(the machine is pscgate, the IP address is 192.77.186.1,
and the patch is in /ftp/pub/patch/v8dd7)
Download V8DD7 from the DOS area on Progress Software
Corporation´s On-Line! Bulletin
Board (617-275-4666 @ 1200,2400, or 9600 baud)
Newkw68 File added to DLC Dictionary
Release Note Number: 80AC-10121
Progress Software Corporation has added a new keyword file,
newkw68 which contains all new reserved keywords that have
been added to the 4GL since Version 6.2. Use the newkw68 file
with the -k startup parameter to inform the PROGRESS compiler
to bypass the new reserved words. When you convert from Version 6
to Version 8.0A02, use the newkw68 file instead of newkywd.
Installation Issue
The following section describes an installation issue.
Installation Utility Update
Release Note Number: 80AC-10163
The Installation utility for PROGRESS Version 8.0A02 for MS-Windows
might incorrectly prompt you for a "Quick Start System" diskette.
If this occurs, insert the corresponding Installation Utility
diskette. For example, if the Installation utility prompts you
to insert Quick Start System diskette number 1, insert
Installation utility diskette number 1.
4GL Issues
The following sections describe functionality that works differently
than in previous releases.
New CAREFUL-PAINT Frame Attribute
Validation Behavior with ENABLE ALL Statement
WORD-WRAP Attribute and Large Editor
Field List Disable (-fldisable) Startup Parameter
XREF Option
Sequential Fonts
DISPLAY Statement Syntax
New CAREFUL-PAINT Frame Attribute
Release Note Number: 80AC-20169
This release includes the new CAREFUL-PAINT read/write attribute
for frames. By default, PROGRESS uses the value of the CarefulPaint
setting in the Startup section of your progress.ini
file to determine the value of the CAREFUL-PAINT attribute.
By default, the value of CarefulPaint is yes, specifying that the
frame paints correctly even if the frame is 3-D and widgets in
the frame overlap.
If you set the value of CarefulPaint to no, widgets that overlap
in a 3-D frame might paintincorrectly, but they paint faster.
You can override the value of the CarefulPaint setting for an
individual frame, if you explicitly set the CAREFUL-PAINT
attribute for that frame.
You can set this frame attribute at any time.
Validation Behavior with ENABLE ALL Statement
Release Note Number: 80AC-10123
The Frame Validation Section of the PROGRESS Programming Handbook
incorrectly states the validation behavior when you use the ENABLE
ALL statement. When your compiler reaches an ENABLE ALL statement,
it compiles Data Dictionary validation into the frame for every
field that has been added up to that point. If all fields that
need validation are in the frame when the compiler encounters
the ENABLE ALL statement, all validation is protected. However
if you use ENABLE ALL with the EXCEPT option, the fields listed
after EXCEPT will not have Data Dictionary validation compiled in.
WORD-WRAP Attribute and Large Editor
Release Note Number: 80AC-10122
In MS-DOS (only), Word-wrap and the WORD-WRAP attribute are not
supported with the Windows large editor. That is, if you set the
LARGE attribute to true for an editor, setting the WORD-WRAP
attribute has no effect.
Field List Disable (-fldisable) Startup Parameter
Release Note Number: 80AC-10140
Field List Disable (-fldisable) is a run-time parameter that
causes PROGRESS to ignore field lists in the r-code and fetch
complete records. It is a client session parameter.
See the PROGRESS Programming Handbook for more information
about using field lists.
XREF Option
Release Note Number: 80AC-10164
The XREF option produces sorting information for queries
containing a BY clause. If it contains expressions or functions
such as:
FOR EACH customer BY RECID (customer)
the following is produced:
s.p. s.p 1 SORT-BY-EXP
If the expression contains a reference to a database field,
the SORT-BY-EXP is also preceded by:
s.p s.p 1 SORT-ACCESS d.customer field
Sequential Fonts
Release Note Number: 80AC-10148
When you add fonts in the fonts section of the progress.ini
file, add font numbers sequentially without spaces or gaps to
avoid the PROGRESS error message.
Font nn not in Font Set (4499)
DISPLAY Statement Syntax
Release Note Number: 80AC-10149
The DISPLAY Statement now accepts the NO-ERROR option.
International Issues
The following sections describe internationalization and
localization issues.
À CColation Tables Update
À Codepage Parameter of the PROLIB Utility
À The PROLIB Utility
À Changing the Code Page of a Database from Undefined
Collation Tables Update
Release Note Number: 80AC-10128
There are variances in some collations between Version 6,
Version 7.2 and Version 7.301.
Note: Version 7.3C01 and Version 8.0A02 are the same.
The following table lists the code pages that PROGRESS
supports and their corresponding collation names and languages.
Code Page Name Collation Name Languages
1250 CZECH Czech, Slovak
1250 HUNGARIAN Hungarian
1250 POLISH Polish
1250 ROMANIAN Romanian
1251 RUSSIAN Russian
1253 GREEK Greek
1254 TURKISH Turkish
1256 BASIC Arabic
620-2533 THAI Thai
708 BASIC Arabic
709 BASIC Arabic
710 BASIC Arabic
711 BASIC Arabic
714 BASIC Arabic
720 BASIC Arabic
721 BASIC Arabic
786 BASIC Arabic
BIG-5 BASIC Traditional Chinese
GB2312 BASIC Simplified Chinese
IBM437 BASIC Basic
IBM850 72-BASIC Version 7.2 Basic
IBM850 BASIC Western Europe and the
Americas
IBM850 DANISH Danish
IBM850 FINNISH Finnish
IBM850 GERMAN-LIBRARY German
IBM850 ICELANDIC Icelandic
IBM850 NORWEGIAN Norwegian
IBM850 SWEDISH Swedish
IBM851 GREEK Greek
IBM852 CZECH Czech, Slovak
IBM852 HUNGARIAN Hungarian
IBM852 POLISH Polish
IBM852 ROMANIAN Romanian
IBM857 TURKISH Turkish
IBM861 ICELANDIC Icelandic
IBM862 HEBREW Hebrew
IBM866 RUSSIAN Russian
ISO8859-1 72- BASIC Version 7.2 Basic
ISO8859-1 BASIC Basic
ISO8859-1 CZECH Czech, Slovak
ISO8859-1 DANISH Danish
ISO8859-1 FINNISH Finnish
ISO8859-1 GERMAN - LIBRARY German
ISO8859-1 ICELANDIC Icelandic
ISO8859-1 NORWEGIAN Norwegian
ISO8859-1 SWEDISH Swedish
ISO8859-1 V6-BASIC Version 6 Basic
ISO8859-1 V6- DANISH Version 6 Danish
ISO8859-1 V6- SWEDISH Version 6 Swedish
ISO8859-2 CZECH Czech, Slovak
ISO8859-2 HUNGARIAN Hungarian
ISO8859-2 POLISH Polish
ISO8859-2 ROMANIAN Romanian
ISO8859-5 RUSSIAN Russian
ISO8859-8 HEBREW Hebrew
KOI8 RUSSIAN Russian
KSC5601 BASIC Korean
MAZOVIA POLISH Polish
ROMAN-8 BASIC Basic
ROMAN-8 CZECH Czech, Slovak
SHIFT- JIS BASIC Japanese
undefined BASIC Basic
undefined V6-BASIC Version 6 Basic
undefined V6-DANISH Version 6 Danish
undefined V6-SWEDISH Version 6 Swedish
The following table lists the conversions that the convmap.cp
file supports. It is an up-to-date edition of Table A-2 in the
PROGRESS System Administration Guide.
Source Code Page Target Code Page Comments
1250 IBM852 Czech Republic,
Slovakia,Hungary,
Poland, Romania
1250 ISO8859-2 Czech Republic, Slovakia,
Hungary, Poland, Romania
1250 MAZOVIA Poland
1251 IBM866 Cyrillic
1251 ISO8859-5 Cyrillic
1251 KOI8-r Cyrillic
1253 IBM851 Greece
1254 IBM857 Turkey
1256 708 Arabic countries
1256 709 Arabic countries
1256 710 Arabic countries
1256 711 Arabic countries
1256 714 Arabic countries
1256 720 Arabic countries
1256 721 Arabic countries
1256 786 Arabic countries
708 1256 Arabic countries
709 1256 Arabic countries
710 1256 Arabic countries
711 1256 Arabic countries
714 1256 Arabic countries
720 1256 Arabic countries
721 1256 Arabic countries
786 1256 Arabic countries
GERMAN-7-bit ISO8859-1 Western Europe and Americas
For 7-bit terminals and -cpterm
conversions only
IBM037 IBM850 AS/400
IBM037 ISO8859-1 AS/400
IBM278 IBM850 AS/400
IBM278 ISO8859-1 AS/400
IBM437 IBM850 Western Europe and Americas
IBM437 ISO8859-1 Western Europe and Americas
IBM500 IBM850 AS/400
IBM500 ISO8859-1 AS/400
IBM850 IBM037 AS/400
IBM850 IBM278 AS/400
IBM850 IBM437 Western Europe and Americas
IBM850 IBM500 AS/400
IBM850 IBM861 Iceland
IBM850 ISO8859-1 Western Europe and Americas
IBM851 1253 Greece
IBM852 1250 Czech Republic, Slovakia,
Hungary, Poland, Romania
IBM852 ISO8859-2 Czech Republic, Slovakia,
Hungary, Poland, Romania
IBM852 MAZOVIA Poland
IBM857 1254 Turkey
IBM861 IBM850 Iceland
IBM861 ISO8859-1 Iceland
ISO8859 ISO8859-8 Israel
IBM862 1251 Cyrillic
IBM866 ISO8859-5 Cyrillic
IBM866 KOI8-r Cyrillic
IBM866 GERMAN-7-bit Western Europe and Americas
For 7- bit terminals
and -cpterm conversions only
ISO8859-1 IBM037 AS/400
ISO8859-1 IBM278 AS/400
ISO8859-1 IBM437 Western Europe and Americas
ISO8859-1 IBM500 AS/400
ISO8859-1 IBM850 Western Europe and Americas
ISO8859-1 IBM861 Iceland
ISO8859-1 ISO8859-1 Western Europe and Americas
ISO8859-1 ROMAN-8 Western Europe and Americas
ISO8859-1 SWEDISH-7-bit Western Europe and Americas
For 7-bit terminals
and -cpterm conversions only
ISO8859-2 1250 Czech Republic, Slovakia,
Hungary, Poland, Romania
ISO8859-2 IBM852 Czech Republic, Slovakia,
Hungary, Poland, Romania
ISO8859-2 MAZOVIA Poland
ISO8859-5 1251 Cyrillic
ISO8859-5 IBM866 Cyrillic
ISO8859-5 KO18-r Cyrillic
ISO8859-8 IBM862 Israel
KOI8-r 1251 Cyrillic
KOI8-r IBM866 Cyrillic
KOI8-r ISO8859-5 Cyrillic
MAZOVIA 1250 Poland
MAZOVIA IBM852 Poland
MAZOVIA ISO8859-2 Poland
ROMAN-8 ISO8859-1 Western Europe and Americas
SWEDISH-7-bit ISO8859-1 Western Europe and Americas
For 7-bit terminals
and -cpterm conversions only
Codepage Parameter of the PROLIB Utility
Release Note Number: 80AC-10143
The -codepage parameter is used in combination with the -create
parameter to specify a codepage for the new library. If you do not
use -codepage, PROGRESS marks the library with the codepage value
of the Internal Codepage (-cpinternal) startup parameter
(ISO8859-1 by default).
For more information about -codepage, see the PROGRESS
System Administration Guide.
The PROLIB Utility
Release Note Number: 80AC-10145
If your filename contains 8 bit characters, the utility
PROLIB library-name -add list-of-filenames does not work
properly and PROGRESS generates the following error message.
Can´t find file filename (1905)
Changing the Code Page of a Database from Undefined
Release Note Number: 80AC-10162
When you change the code page of a database from "undefined"
using the utility PROUTIL dbname -C convchar convert codepage,
PROGRESS generates the following warnings:
Conversion beginning, please await success confirmation...(1100)
The database codepage is "undefined". (1170)
Modifying the database code page name only. (1171)
No data conversion will take place. (1196)
The current collation table is not compatible with the database
code page. (2899)
Note: You should also load the _tran (.df) file and the
collations afterwards.
User Interface Builder Issues
The following sections describe issues that affect the User
Interface Builder (UIB).
À Changes to the ADM Since 8.0A
À Copy Templates
À ADM GET Methods Update
À Procedure Editor Date Formats in the UIB
À Adding Buttons or Objects
À AllowDesignMode Parameter
Changes to the ADM Since 8.0A
Release Note Number: 80AC-20173
Note: You only need to read this section if you:
À Have upgraded from PROGRESS Version 8.0A to Version 8.0A02.
À Are building SmartObjects and modifying the SmartObject files shipped
with PROGRESS Version 8.
The following list describes the changes to Version 8.0A02 since
8.0A. These changes address
the 8.0A issue in which an update that has generated an error
should not end until the error is
corrected or the update is canceled by the user. In 8.0A, the
update is generally canceled by the
ADM if a local assign method returns ERROR or if there is a
validation error or a database
trigger failure.
If you have modified any of the include files listed here or
built new SmartPanels based on those shipped with the product
you must reconcile them with these changes. For example, if
you built a new SmartPanel which adds additional buttons or
removes some of the standard buttons, you should make the
same button changes to the Update SmartPanels shipped with 8.0A02.
List of Changes by File:
dlc/src/adm/method/attribut.i
Added the definition for the new adm-updating-record variable.
This variable is reserved for future use and does not have an
effect in 8.0A02. However, it is required by changes to tableio.i.
dlc/src/adm/method/tableio.i
Added code that sets and clears the new adm-updating-record
variable. Removed the code in the adm-assign-record event procedure
which deleted the current browser row on an error in an Add operation.
Added an ON ERROR UNDO, RETURN "ADM-ERROR" phrase to the
TRANSACTION block in the adm-update-record event procedure.
This new phrase captures database trigger failures which are
detected at the end of the block. Removed the update-failed
variable from the adm-end-update event procedure so that this
procedure does not complete if there is an error.
Changed the set-editors procedure to allow it to clear editor
widgets when initial values are displayed for a record Add operation.
(As in Version 8.0A, initial values can be displayed for
enabled fill-in field widgets, but not for other widgets.)
dlc/src/adm/template/brsleave.i
Added the IF RETURN-VALUE = "ADM-ERROR" THEN RETURN NO-APPLY
statement. This statement leaves focus in the current row
until the error is corrected or the update is canceled.
dlc/src/adm/objects/p-updsav.w
À Added code that resets the Update/Save button label from
the set-buttons procedure instead of the individual button triggers.
This code change makes the SmartPanel wait until the tableio-
target object successfully completes the action and sends
back a state of ´update-complete´. Made cosmetic cleanup changes.
dlc/src/adm/objects/p-updtxn.w
Added code that resets the Update/Save button label from the
set-buttons procedure instead of
the individual button triggers. This code change makes the
SmartPanel wait until the tableio-target object successfully
completes the action and sends back a state of ´update-complete´.
Changed the code in the Commit button trigger so that the
transaction ends only if the RETURN-VALUE is not ADM-ERROR.
Made cosmetic cleanup changes.
Copy Templates
Release Note Number: 80AC-10125
Before installing PROGRESS Version 8.0A02, copy any of the
following Version 7 templates that you want to retain to an
area outside of the DLC directory. Some Version 7 templates
(those listed below) that reside in
G:\V8\WIN\80A02\DLC\src\template are no longer supplied with
Version 8.0A02.
childwin.w dlgrecup.w navread.xpm
custdemo.txt doaction.i navreadi.xpm
dbopsupp.i mainwin.w navupd.xpm
deffrupd.i menu-bar.w navuprec.xpm
detail.xpm mainwin.xpm order.xpm
dlgclose.xpm menu-bar.xpm orderlin.xpm
dlgokcan.xpm navicons.wx order.wx
dlgrecup.xpm navigate.wx orderlin.wx
childwin.xpm navread.w templdef.i
custom.txt navreadi.w winbrows.xpm
defbrupd.i navupd.w winbrows.w
detail.w navuprec.w
dlgclose.w navicons.xpm
dlgokcan.w navigate.xpm
Note: The custom.txt file is a subset of
G:\V8\WIN\80A02\DLC\src\template\progress.cst,
which is delivered with Version 8.0A02.
ADM GET Methods Update
Release Note Number: 80AC-10129
Two ADM methods available in Beta Version 8 have been
replaced with attributes. GET-ATTRIBUTE ("CURRENT-PAGE")
replaces GET-CURRENT-PAGE and GET-ATTRIBUTE ("ADM-OBJECT-HANDLE")
replaces GET-OBJECT-HANDLE.
Note: This is a change from the 8.0A1P Release Notes.
Procedure Editor Date Formats in the UIB
Release Note Number: 80AC-10150
If you run the PROGRESS Procedure Editor from the Tools menu
in the UIB, the "-y dmy" (Date Format startup parameter) change
will not be recognized. The default date format specification,
"-y dmy", is used.
Workaround: Use the Procedure Editor from the PROGRESS
Desktop Tool bar, not from the UIB.
Adding Buttons or Objects
Release Note Number: 80AC-10134
If you add buttons or other objects to a SmartPanel, PROGRESS
does not enable them. For example, if you add a Done button
to a SmartPanel, it comes up disabled.
Workaround: Put the statement, "RUN dispatch (´enable´:u)",
as the first statement in local-enable when you add buttons or
other objects to a SmartPanel.
AllowDesignMode Parameter
Release Note Number: 80AC-10152
When you deploy applications that use VBX controls, set the
following line in the [Startup] section of the progress.ini file:
AllowDesignMode=No
This allows the VBX controls to function properly without license files.
Browse Widget Issues
The following sections describe issues that affect browse widgets.
NEW SHARED BROWSE Not Scrolling
Browse Widget Method Restrictions
Empty Browse Widget
Defining an Updatable Browse Widget
NEW SHARED BROWSE Not Scrolling
Release Note Number: 80AP-10116
If you define a NEW SHARED BROWSE, query, and buffer, PROGRESS
does not automatically make the associated query a scrolling query.
You must explicitly define the query as SCROLLING in the DEFINE NEW
SHARED query statement.
Browse Widget Method Restrictions
Release Note Number: 80AC-10151
You cannot assign the values of the field in the browse widget
and then apply the CREATE-RESULT-LIST-ENTRY() method in one statement.
The compiler generates an error message if you do.
Workaround: Make them two separate statements such as:
ASSIGN INPUT BROWSE browse-1 name address phone.
log = BROWSE browse-1:CREATE-RESULT-LIST-ENTRY().
Empty Browse Widget
Release Note Number: 80AC-10147
By default you cannot insert data into an empty browse widget.
For more information on browse widgets, refer to the PROGRESS
Programming Handbook, Chapter 9.
Defining an Updatable Browse Widget
Release Note Number: 80AC-10137
When you attempt to define an updatable browse widget, if the
definition explicitly references a table but no fields and you
attempt to update a field, PROGRESS returns a fatal error.
For example, trying to update a field in the following browse
causes a fatal error:
DEFINE BROWSE browse-1
QUERY query-1
DISPLAY customer
ENABLE ALL WITH SIZE 60 BY 5.
Note: Updatable browse code written in previous versions of
PROGRESS or UIB generated code written in Version 8.0A02 is not
affected by this issue.
Workaround: Be explicit when you reference table fields in
the updatable browse widget definition statement. For example:
DEFINE BROWSE browse-1
QUERY query-1.
DISPLAY name address
ENABLE all WITH SIZE 60 by 5.
Translation Manager Issues
The following sections describe issues related to the Translation
Manager tool.
Closing Resource Procedures in the Visual Translator
Context-sensitive Help
Translating SmartObject Tab Folders
Security Restrictions on Databases
Adjusting Justification on Database Fields
Closing Resource Procedures in the Visual Translator
Release Note Number: 80AC-20172
In the Visual Translator, when you visualize a resource procedure,
it does not receive focus. If
you want to close the resource procedure, you must first click on
the resource procedure window to give it focus.
Context-sensitive Help
Release Note Number: 80AC-20168
In the Translation Manager and Visual Translator tools, if you
select the Help tool-bar button, buttons and objects that do not
have help sections (as indicated by the display of the cursor)
launch the function of the object if you do choose them.
For example, in the Translation Manager, if you choose the Help
tool-bar button, then choose the Add action button in the Glossaries
tab folder, the Add Glossary dialog box appears instead of help
information about the Add button.
Translating SmartObject Tab Folders
Release Note Number: 80A4-20111
In this release, the User Interface Builder (UIB) marks SmartObject
tab folder labels as untranslatable (:U). Because the text strings
for the tab folder labels are marked :U, the Translation Manager
does not extract them and, therefore, does not translate them.
To make UIB-generated tab folders translatable, follow these steps.
1. In the UIB, open the procedure that contains the SmartObject tab folder.
2. Choose Code on the UIB toolbar. The Section Editor appears.
3. From the Section combo-box list, select Procedures.
4. Choose New. The New Procedure dialog box appears.
5. Activate the Local ADM Event radio button.
6. From the Source combo-box list, select adm-initialize, then choose
OK. A shell
procedure called local-initialize appears in the Section Editor.
7. Insert the cursor after the following line of code:
/* Code placed here will execute PRIOR to standard behavior. */
Note: There are more lines of code further down in the shell
procedure concerning
dispatching the standard ADM method. Make sure you place
the cursor before these
lines of code.
8. Type code similar to the following example code. In this
example, Customer, Shipment,
Order, and Catalog are the labels for the tab folder.
RUN set-attribute-list IN h_folder
("folder-labels = ":U + "Customer" + "|":U + "Shipment"
+ "|":U + "Order" + "|":U + Catalog").
9. Choose Close from the File menu to exit the Section Editor.
10. Save your changes when you close the procedure or exit the UIB.
Security Restrictions on Databases
Release Note Number: 80AC-20167
When you use the Compile option to compile source code in the
Translation Manager, the Translation Manager is connected to more
than one database - the project database and the application database.
If you use the SETUSERID function to define security for the source
code databases and you do not specify the logical-dbname parameter,
the Compiler generates error messages.
Workaround: Explicitly define the logical database name of the
application database in the SETUSERID function.
Adjusting Justification on Database Fields
Release Note Number: 80AC-20166
Many PROGRESS 4GL applications derive text labels form the
PROGRESS database they access. There is a good chance that,
like the Sports database, the fields in the database are left-justified.
This does not present a problem for the user-interface in
the English source language, but after translation, it can cause
layout problems.
To avoid these layout problems, you should apply the TRIM string
attribute to trim the database fields for side-labels. If you have
multiple fields that you need to trim, you can run the following
small 4GL application to automatically trim the fields for you.
FOR EACH _field WHERE NOT _field._field-name BEGINS "_":U
AND _field._label-SA = ?:
_field._label-SA = "T":U.
END
Report Builder Issues
The following sections describe issues related to the Report Builder tool.
CBT Course Requirements
CBT Courses on Windows 95
International Versions of Report Builder
Selecting Sort Fields with Report Builder
Report Builder Users Guide Update
-d and -E Startup Parameters
Memo Fields with Large Tables
Set UNKNOWN Value Dialog Box
CBT Course Requirements
Release Note Number: 80AC-20165
The following information is not included in the PROGRESS Version 8
Installation Notes for Windows.
Terminal Requirements
You must run the following Computer-based Training (CBT) courses
on a 640 x 480 screen resolution with a 256 color palette
Getting Started with Report Builder
Mastering Report Builder
Disk Space Requirements
The approximate disk space requirements for these CBT courses are:
Getting Started with Report Builder - 20 MB
Mastering Report Builder - 46 MB
Icon Commands
The commands for the Report Builder CBT icons are:
Getting Started with Report Builder
<installation-path>\cbt\rb\present\present.exe ..\iconware\rb.iwm
Mastering Report Builder
<installation-path>\cbt\mrb\present\present.exe ..\iconware\mrb.iwm
CBT Courses on Windows 95
Release Note Number: 80AC-20171
If you run the ´Getting Started with Report Builder´ CBT or the
´Mastering Report Builder´ CBT on Windows 95, some objects in the
CBT display might not line up properly.
International Versions of Report Builder
Report Builder for PROGRESS Version 8.0A is available in English as
well as the following translations:
Czech
German
Hebrew
Russian
Spanish
Swedish
Each of the six translations is incorporated in a single .DLL named
RBESxxx.DLL, where "xxx" is an abbreviation for a language. For example,
the German translation is contained in the RBRESGER.DLL file.
(The English version is simply RBRES.DLL.)
The .DLL files are stored in the appropriate DLC\PROLANG directory.
For example, the full filename of the German translation is
DLC\PROLANG\RBRESGER.DLL. To enable a translation, install
"International PROMSGS" for the appropriate language.
For a complete discussion on using a translated version of Report
Builder, see appendix B of the PROGRESS Report Builder User´s Guide.
Selecting Sort Fields with Report Builder
Release Note Number: 80A3-20079
Report Builder permits you to select the following fields as sort
fields. If you select these fields as sort fields, the Report Builder
might generate incorrect report output or other errors.
Calculated fields that use the PAGE-NUMBER, RECORD-NUMBER or
PREVIOUS
function.
Self-referencing calculated fields.
Workaround: Avoid selecting these types of fields as sort fields.
Do not group on a calculated field that uses the PAGE-NUMBER or
PREVIOUS function.
Report Builder Users Guide Update
Release Note Number: 80AC-10126
The User-defined Functions chapter of the Report Builder User´s
Guide incorrectly indicates that if no prorb.udf file exists when
you create a new user-defined function, the Report Builder will
create the prorb.udf file in the program directory by default.
It should say that the Report Builder will create the prorb.udf
file in the directory in which the progress.ini file was found by default.
Note: To specify an alternative directory where the prorb.udf
file should be created, set the UDFDirectory parameter in the
[ReportBuilderDefaults] section of progress.ini.
-d and -E Startup Parameters
Release Note Number 80AC-10127
Although the -d and -E parameters are now recognized, their
settings only affect the report output and several built-in functions.
The -d and -E settings are not used to process numeric and date input
as all numeric and date constants used in a report (as part of a filter,
UDF expression or calculated field) must be in American format.
The STRING, NUMERIC and DATE built-in functions use the -d and -E
settings as follows:
STRING: Returns a result string that is in the format specified by -d
or -E.
NUMERIC: Expects a character argument that is in the European
format (-E) if -E is used. For example: NUMERIC("5,25")
DATE: Expects a character argument that represents a date
in the format specified by -d. For example: DATE("9/11/95")
Memo Fields with Large Tables
Release Note Number: 80AC-10144
If your report contains memo fields from an attached memo file,
the Report Builder generates a SELECT statement that includes all
fields from all tables used in the report. If your tables contain
many fields, this might cause poor performance and will cause an
error if the SELECT statement is too long.
Workaround: A setting in the [ReportBuilderDefaults] section
of the progress.ini file called MemoMinimumSelect, when set to a
non-zero value, prevents Report Builder from fetching all fields
in all tables when a memo field is present. However, if your memo
contains embedded fields that are not used elsewhere in the report
definition, they are not fetched from the database and display as unknown.
Set UNKNOWN Value Dialog Box
Release Note Number: 80AC-10130
If you specify an empty value in the Set UNKNOWN Value dialog
box for a field, when Report Builder opens the report, it assumes
you want to use the default display value (?) for any unknown values
in that field.
Workaround: If you do not want to display anything for field
values that are UNKNOWN, specify a single blank space in the Set
UNKNOWN Value dialog box.
DataServer Issues
The following sections describe issues that apply to DataServer products.
ORACLE: SELECT Pass Through Function
ORACLE: varchar2 Parameter
SYBASE4: ldemo Script
SYBASE4 and SYBASE10: PROBUILD Link Script
C-ISAM: ROWID Function
ORACLE: SQL*Net DLL Files
SELECT Pass Through Disable (-noSQLbyserver)
ORACLE: SELECT Pass Through Function
Release Note Number: 80A3-20088
The following types of SELECT statements are not executed on the
ORACLE server:
SELECT statements that include tables with FIND triggers
will not be passed through to the ORACLE server.
Queries that contain references to extents, for example:
SELECT mnth-sales[i] FROM customer WHERE cust-num = 1.
SELECT mnth-sales FROM customer.
Queries that contain references to more than one database,
for example:
SELECT db1.customer.name,db2.order.cust_num
FROM db1.customer,db2.order
WHERE db1.customer.cust-num = db1.customer.cust_num.
Queries that contain GROUP BY with an ORDER BY, for example:
SELECT MAX (max-credit), st
FROM customer GROUP BY st ORDER BY 2 DESCENDING.
Queries containing functions that are not supported by the
ORACLE data manager, for example:
SELECT LEFT-TRIM(name, "S") FROM customer.
ORACLE: varchar2 Parameter
Release Note Number: 80A1-20058
ORACLE does not provide size information for stored procedure
parameters. If you want to pass more than 255 bytes for a varchar2
parameter, you must change the schema holder and set the _for-maxsize
field for the varchar2 parameter.
SYBASE4: ldemo Script
Release Note Number: 80A1-20061
You cannot run the SYBASE4 DataServer ldemo script from a Windows
client. ldemo is a UNIX script.
SYBASE4 and SYBASE10: PROBUILD Link Script
Release Note Number: 80A1-20063
If you use PROBUILD to create a link script that includes both the
SYBASE4 and SYBASE10 DataServers in a single executable, PROBUILD
includes $SYBLIB twice.
Workaround: Remove the second instance of $SYBLIB from the
PROBUILD-generated link script.
C-ISAM: ROWID Function
Release Note Number: 80AC-10138
The C-ISAM DataServer for Version 8.0A02 includes support for the new
ROWID function. See the PROGRESS Language Reference for details on how
to use this new function.
ORACLE: SQL*Net DLL Files
Release Note Number: 80AC-10136
When you attempt an ORACLE SQL*Net connection, PROGRESS searches your
PATH for SQL*Net DLLs in the following order:
À ora72win.dll - SQL*Net V2.2
À ora71win.dll - SQL*Net V2.1
À ora7win.dll - SQL*Net V2.0
If you have both ora7win.dll and ora71win.dll on your PATH, PROGRESS
uses the latest version of SQL*Net (ora71win.dll - SQL*Net V2.1).
This differs from PROGRESS Version 7 which only uses ora7win.dll
(SQL*Net V2.0).
Because of this, a PROGRESS client will always use the latest version
of SQL*Net installed on a system, as determined by the current PATH
setting and the availability of the above named DLLs. If you need to
use an older version of SQL*Net, you should make sure that any DLL´s
for newer versions of SQL*Net are not on the PATH. To do this, rename
the other DLLs.
Note: Most ORACLE products depend on a specific version of SQL*Net.
You might have different versions of SQL*Net, and thereby require more
than one ora7xwin.dll file to be present on your PATH to work. By
renaming a DLL file or taking it off your PATH, you might cause some
ORACLE tools to stop working.
SELECT Pass Through Disable (-noSQLbyserver)
Release Note Number: 80AC-10142
You can use SELECT Pass Through Disable (-noSQLbyserver) to turn off
SELECT Pass Through for the current PROGRESS session. It is a client
session parameter.
See your PROGRESS DataServer Guide for more information.
GUI RESULTS Issue
The following section describes an issue that affects GUI RESULTS.
Integration Procedures
Release Note Number: 80AC-10124
The following is the sequence for the integration procedures run at
the startup of RESULTS.
1. u-define.p
2. u-logo.p
3. u-login.p
4. u-secure.p
5. u-table.p
ODBC Driver Issues
The following sections describe issues that affect the ODBC Driver.
Memory Allocation Routines
Convmap.cp File
Decimal Data Fields
Memory Allocation Routines
Release Note Number: 80AC-10132
Because of extensive modifications to the low level memory allocation
routines, PROGRESS might generate a GPF if an attempt is made to access
uninitialized memory. If you encounter this issue, please contact
Progress Technical Support.
Convmap.cp File
Release Note Number: 80AC-10133
In both the ODBC Driver and ESQL small client, the Open Interface
Driver (OID) will fail with a GPF if the convmap.cp file is not
present. If this file is missing, look for it in your DLC directory
or if it is not in this directory, reinstall PROGRESS Version 8.0A02.
If both of these fail, contact Progress Technical Support.
Decimal Data Fields
Release Note Number: 80AC-10139
When you use a Visual Basic application to insert new records that
contains column(s) with decimal data fields, if all the fields are
not filled in, PROGRESS generates a GPF.
Workaround: Be sure to fill in all fields.
Transaction Support
Release Note Number: 80AC-10146
Visual Basic applications that require transaction support for
BeginTrans, CommitTrans and Rollback methods will fail without
generating an error message.
Workaround: Contact Progress Technical Support for a patch
to this issue.
WIN95 Issues
The following sections describe issues that affect the WIN95
Operating System.
IPX/SPX Connection
Long Filename Directories
Fonts and Font Size
PSOLE VBX Control
IN_PLACE_ACTIVATION Event
User List
Frames and Browse Widgets
Combo Boxes
IPX/SPX Connection
Release Note Number: 80AC-10135
Install the file nwipxspx.dll in your system directory or at
least along the path in order for an IPX/SPX connection to
function properly.
Long Filename Directories
Release Note Number: 80AC-10153
Program files or databases stored in directories named with long
filenames cannot be opened or retrieved. The tilde character (~),
used by WIN95 with long filenames, is a special PROGRESS escape character.
Fonts and Font Size
Release Note Number: 80AC-10154
In WIN95, system fonts and font size can be user-defined. In
Version 8.0A02, PROGRESS does not adjust containers according to the
size of the font.
PSOLE VBX Control
Release Note Number: 80AC-10155
The PSOLE VBX control generates a set property failure when you
execute a ReadFromFile or a SaveToFile across a network drive.
IN_PLACE_ACTIVATION Event
Release Note Number: 80AC-10156
The MediaClip.VBX does not activate an IN_PLACE_ACTIVATION event.
User List
Release Note Number: 80AC-10157
If you are connected to a database without a User List, the PROGRESS
USERID(db-name) function returns a blank name instead of the person
who is logged into the windows session.
Frames and Browse Widgets
Release Note Number: 80AC-10158
PROGRESS frames and browse widgets whose TITLE attributes are set,
display a disabled "close X" icon at the right side of the TITLE bar.
This icon should be disregarded as it cannot be enabled.
Combo Boxes
Release Note Number: 80AC-10159
In WIN95, PROGRESS adds a scroll bar to the combo box instead of
letting it remain the precise size as LIST-ITEMS. This occurs because
the user default font is user definable and is not the system font.
Workaround: If you explicitly set the default font to be the
system font, PROGRESS displays the combo box correctly.
Progress Software Technical Support Note # 15597