MS-Windows 7.3A Release Notes Commercial Release readme.pro
PROGRESS VERSION 7.3A RELEASE NOTES
PLATFORM: MS-Windows v3.1
MEDIA TYPE: 3-1/2" Diskette
SOFTWARE RELEASE: 7.3A
EXTRACT COMMAND: (Not applicable)
INSTALL COMMAND: WIN DRIVE_LETTER:install
** IMPORTANT **
You must truncate the before-image file of all PROGRESS
Version 6 databases before you convert the databases to
PROGRESS Version 7.3A. See the "PROGRESS System Administration
Guide" and "Progress System Administration Reference" for details
on how to truncate the PROGRESS before-image file.
Due to R-CODE changes made between Version 7.2 and Version 7.3A,
you must recompile your applications.
** IMPORTANT NOTICE TO 7.3A BETA USERS **
Due to R-CODE changes you must recompile your applications.
These release notes include other important information.
Please read this entire document before you work with PROGRESS
7.3A.
========
CONTENTS
========
1. Product Compatibility for Version 7.3A
2. Installation Issues
3. Networking Issues
4. DOS and MS-Windows Issues
5. ISO Latin Character Set 8859-1 Support in the Sports
Database
6. The PROGRESS Messages File (PROMSGS)
7. ADE Issues
A. User Interface Builder
B. Report Builder
8. GUI/Language Issues
A. General GUI/Language Issues
B. ESQL/C
9. Remote Dataserver Issues
A. ORACLE Remote DataServer
B. AS/400 Remote DataServer
10. R-code Portability
11. Internationalization Issues
A. Character Set Management Issues
B. Double Byte Enablement Issues
C. Report Builder Internationalization
D. Miscellaneous Internationalization Issues
12. Known Problems:
A. User Count with DDE Server
B. Networking
C. User Interface/Widgets
D. ADE
E. User Interface Builder
F. Language
G. Procedure Editor
H. Librarian
I. Data Dictionary
J. Data Administration
K. Application Compiler
L. Translation Manager
M. Utilities
N. ESQL/C
O. Internationalization
P. Portable R-code
Q. PROBUILD
R. DataServers
S. RESULTS
T. Report Builder
=========================================
1. PRODUCT COMPATIBILITY FOR VERSION 7.3A
=========================================
For complete compatibility among all product components,
it is essential when running Version 7.3A that all
products be at that version level. The exception is the
PROGRESS Server Product, which may be of an earlier version
than the connecting Client product.
For instance, a Version 7.3A client can connect to a
Version 7.2D server, or a Version 7.3A client can connect
to a Version 6.2M server.
======================
2. INSTALLATION ISSUES
======================
Progress Software recommends that you do not store databases,
before-image (.bi) files, or after-image (.ai) files on compressed
disks. Database integrity cannot be maintained and your
database might be damaged.
* ENVIRONMENT VARIABLES
Remove all environment variables set up for earlier versions
of PROGRESS before you run PROGRESS Version 7.3A.
Append directories which need to be included in the PROPATH
environment variable (for example, the working directory
denoted for the PROGRESS icons) onto the current definition
of PROPATH in the PROGRESS.INI file. The PROGRESS.INI
file is located in the C:\G:\V7\WIN\73A\DLC\BIN directory. If user-specific
PROPATHs are necessary, place unique versions of PROGRESS.INI
in the user´s working directory or use the "-Wa -name"
startup parameter to explicitly denote the location of
the desired PROGRESS.INI file.
If you place C:\G:\V7\WIN\73A\DLC\SRC in the PROPATH environment variable
before the PROGRESS-supplied r-code directories, PROGRESS
might generate unpredictable behavior. At run time, the
following directories are appended onto the current PROPATH
definition: C:\G:\V7\WIN\73A\DLC\GUI, C:\G:\V7\WIN\73A\DLC and C:\G:\V7\WIN\73A\DLC\BIN. PROGRESS
uses these directory segments in the PROPATH to find key r-code
files to run the ADE tools. If you exclude or supersede
these directories, PROGRESS is either unable to run an
ADE tool or it exhibits serious performance degradation.
See the "PROGRESS Version 7.3A Installation Notes" for
information on how to define the DLC environment variable
and alter the PATH environment variable.
* 3-D SUPPORT USING CTL3.DLL
3-D support for widgets requires the use of a DLL called ctl3d.dll.
During installation PROGRESS installs this file in the WINDOWS
directory. The install program first looks in the directory
WINDOWS\SYSTEM to see if the file ctl3d.dll already exists. If
it does, it compares the existing version to the one included
with PROGRESS. It installs a new ctl3d.dll only if the
existing version is older than the new one. If no ctl3d.dll exists
in the target directory, it is also installed there.
* IBM PC SUPPORT
If you use the IBM PC Support product when you install PROGRESS on
your personal computer, you will encounter problems. Make sure the
IBM PC Support product is not running before you install PROGRESS.
* TEXTLESS ICONS
Textless icons are provided with Version 7.3A for international
users. To install these icons, execute the following commands:
CD G:\V7\WIN\73A\DLC\GUI\ADEICON
COPY TEXTLESS\*.* .\*.*
This will replace the installed icons with the textless icons. If
you want to keep the installed icons, be sure to copy them to
a backup location before installation.
====================
3. NETWORKING ISSUES
====================
* THE WINDOWS NETWORK DATABASE SERVER (DDE)
The Windows Network Database Server product provides a
development-only version of the PROGRESS server called
WPROSERV.EXE. This program is NOT meant for use in a production
environment. It exists to allow development teams to test
programs in a multi-user environment. WPROSERV supports
local clients connecting over DDE only.
To start a database server using the WPROSERV facility,
edit the properties of the WPROSERVE icon to include the
database name, the networking protocol (-N DDE) and the
service name (-S) in the command line, if applicable.
Please see the PROGRESS Networks Guide for additional
information.
* TCP/IP PROTOCOL
The _PROWIN.EXE module supports only TCP/IP software packages
for Windows that include support for WINSOCK specification
Version 1.1 (WINSOCK.DLL).
These include but are not limited to:
PC-NFS v5.1
NetManage v4.0
FTP PCTCP v2.3
Novell´s LAN Workplace (or Workgroups) for
DOS/Windows v4.2
The _PROWINL.EXE and related executables (_PROAS4L.EXE and
WPROSHUTL.EXE) are no longer supported. In Version 7.2 these
executables had support for LAN Workplace for DOS´s TCP/IP
propriatary API (wlibsock.dll). Since LAN Workplace v4.2
now supports the WINSOCK API, PROGRESS will no longer provide
separate executables. _PROWIN.EXE can now be run with LAN
Workplace, either as v4.1 with the WINSOCK.DLL or as v4.2.
============================
4. DOS AND MS-WINDOWS ISSUES
============================
* -o STARTUP PARAMETER NO LONGER SUPPORTED
The -o startup parameter is not supported in this release.
OUTPUT TO PRINTER destination can be changed at run-time using
either the Windows Control Panel or the SYSTEM-DIALOG
PRINTER-SETUP 4GL option.
* PROBKUP NO LONGER SUPPORTS THE -o (OVERLAP) STARTUP OPTION
To use an overlap factor with PROBKUP, use the -io option.
* PERFORMANCE DURING BATCH-MODE PROCESSING
To enhance performance during batch-mode processing, Progress
Software suggests that you uncomment the MultiTaskingInterval=100
parameter in the [Startup] section of the PROGRESS.INI
file by removing the leading semicolon and changing the
value to 9999. Use a value of 1000 if you want to run another
application while running PROGRESS in batch mode. Another option
is to set the equivalent session handle by adding the following
to the beginning of the main procedure:
SESSION:MULTITASKING-INTERVAL=0.
* USE OF DOS EDITORS
Several DOS editors (such as edlin and Brief) place a CTRL+Z
at the end of edited files. This can cause unpredictable results
when used on text files that are used with PROGRESS utilities,
for example, CONVMAP.DAT.
* CHANGING PRINTER FONTS IN THE PROGRESS.INI FILE
New, undocumented entries have been introduced for the
PROGRESS.INI file that allow you to change the font used by
the OUTPUT TO PRINTER and OUTPUT TO LPTx statements. The new
entries are placed in the [Startup] section. The key values are:
PrinterFont for use with the OUTPUT TO PRINTER statement.
PrinterFont1 for use with the OUTPUT TO LPT1 statement.
PrinterFont2 for use with OUTPUT TO LPT2 statement.
etc.
The values on the right side of the statements have the
same format as the FONT definitions in the FONT section:
PrinterFont=<facename>[,size=<screen-point-size>]
* OUTPUT TO LPTx
When using the OUTPUT TO LPTx statement, your output will
be sent to the first printer defined in Printer Setup that is
connected to LPTx specified. If you have two printers defined
for LPTx, such as Printer1 and Printer2, output will always print
to Printer1. If you want to output to the default or current
printer, use OUTPUT TO PRINTER.
==============================================================
5. ISO LATIN CHARACTER SET 8859-1 SUPPORT IN THE DEMO DATABASE
==============================================================
See the hard copy release notes for information on 8859-1
support in the demo database.
=======================================
6. THE PROGRESS MESSAGES FILE (PROMSGS)
=======================================
Many users who run PROGRESS in MS-Windows like to
create a DOS shell to run PROGRESS utilities (PROUTIL,
PROSERVE, RFUTIL, etc.). Before doing this, make sure
that the character set of the PROMSGS file is the same
as the one used for your DOS display devices or output
files (that is, your DOS streams).
In fact, you may want to consider using two PROMSGS files
on your system, one for DOS and one for Windows. On DOS,
set the %PROMSGS% environment variable to point to the
DOS-specific PROMSGS file. In Windows, set the %PROMSGS%
environment variable in the PROGRESS.INI file to point
to the Windows-specific PROMSGS file.
=============
7. ADE ISSUES
=============
See the hard-copy release notes for issue pertaining to the ADE.
======================
8. GUI/LANGUAGE ISSUES
======================
8.A General GUI/Language Issues
--------------------------------
* USE OF 3-D DISPLAY WITH VERSION 7.2 FILL-INS
The new "3-D" feature in Version 7.3A adds extra pixels on the
borders of FILL-IN widgets to achieve the three-dimensional effect.
This causes problems with application screens designed on Version
7.2, which were designed without a 3-D feature.
A new PROGRESS.INI parameter has been created, called Use-3D-Size,
to allow the programmer to control how the extra "3-D" pixels are
added to FILL-INs.
When Use-3D-Size = YES, FILL-INs (and PPUs) will be 26 pixels high
instead of 24 pixels, making them 8% taller on the frame. This
displays FILL-INs in 7.3 3-D mode.
When Use-3D-Size = NO, FILL-INs will remain the same size as they
were in Version 7.2, however due to the necessity to add the 3-D
effect their decorations might overlap.
* PUT SCREEN IS NOT SUPPORTED ON MS-WINDOWS
The PUT SCREEN 4GL command is not supported on the MS-Windows GUI
platform.
* WIDGET SHOW-THROUGH WHEN USING 3-D DISPLAY
Widget show-through results when you overlay objects that are displayed
in 3-D. This limitation is one that is imposed by the Microsoft
3D DLL used by PROGRESS, and is not itself a PROGRESS problem.
Therefore, the overlay of 3-D widgets in MS-Windows is not supported
at this time.
Workaround: when creating a widget that will overlay others, place
it on a frame such that the frame does not appear (that is, define
the frame as NO-BOX and NO-TITLE and match its edges with those of
the widget). Using a frame prevents the show-through.
* NEW ATTRIBUTE :KEEP-FRAME-Z-ORDER
A new WINDOW attribute :KEEP-FRAME-Z-ORDER has been added. It is
a logical value which when set to YES will override all default frame
behavior that wants to bring frames to the top of the Z-order. This
attribute will not affect behavior of the :MOVE-TO-TOP() and
:MOVE-TO-BOTTOM() methods.
* OUTPUT TO TERMINAL NOW USES CURRENT-WINDOW
The OUTPUT TO TERMINAL statement will now use the CURRENT-WINDOW
for its output destination.
* DISK FILES CREATED BY EDITOR WIDGETS ON UNIX AND MS-WINDOWS
Editor widgets write to disk differently depending on
whether you are in UNIX or MS-Windows.
In Windows, <Enter> is seen as x0d0d0a. In UNIX this
is x0d0a.
In Windows, the end of a line is denoted by a <CR><LF>.
In UNIX this is a <CR>.
These issues are consequences of using the native widgets
in the different environments. A future version of PROGRESS
will address these issues, allowing for improved portability
among platforms.
* USE OF 246-COLOR BITMAP IMAGES
If you use bitmap images saved in 256-color mode, MS-Windows
attempts to create an individual color map for the image
each time it is realized in PROGRESS. The observed effects
are:
- The background flashes as the color palette is
loaded for each 256-color image, unless the
color map is identical to the one previously loaded.
- Performance degrades.
Convert 256-color bitmaps to 16-color or recreate them
with 16 colors. Note: This behavior is a Windows phenomenon
not specific to PROGRESS.
* USE OF :SCREEN-VALUE ATTRIBUTE BEFORE IT IS TRULY SET
With widgets such as radio-sets, it is possible under certain
conditions to toggle the widget so that it appears to be set
to a certain value while the :SCREEN-VALUE has not in fact
been changed. Any use of the :SCREEN-VALUE attribute under these
conditions will result in a use of a value that does not agree
with what is on-screen. This is due to the way MS-Windows
stacks events and is therefore not a phenomenon specific
to PROGRESS.
Programmers should be sure to design their applications so that
the :SCREEN-VALUE of a widget is never queried or used for record
assignment until the widget has been validly acted upon by
the user.
8.B ESQL/C
-----------
* NEW SQLCODE
A new SQLCODE has been added. A value of (-30) signifies
that the database system has caused the current transaction to be
rolled back.
* PROGRESS SQL DOES NOT READ DESIGNATED .INI FILE
The PROGRESS SQL engine does not read the .INI file designated
in the "-Wa -name" startup parameter. Environment variables set
in the .INI file so designated will not be read. Set all environment
variables at the DOS level prior to starting MS-Windows.
* MIGRATING VERSION 6 HLI CODE TO VERSION 7 ESQL
The following describes the process for migrating Version 6 HLI
code to Version 7 ESQL.
If the application is solely based on the SQL Preprocessor,
do the following:
1. If using dynamic SQL, change the syntax of the DESCRIBE statement
to read "USING SQL DESCRIPTOR"; in Version 6, the "SQL" keyword
isn´t required. In the FETCH statement, change the "USING
DESCRIPTOR" to "INTO SQL DESCRIPTOR".
2. The usage of sqllogout() should be inspected CAREFULLY - it no longer
exits the application.
3. Rerun the preprocessor, recompile, and link (generate a new load
script with PROBUILD - the name of the script has changed). The
locations of the header file, proesql.h and the SQLCPP have changed.
4. If "int" is used as a C declarator for embedded variables, a warning
is now issued about non-standard usage.
If the application uses some or all of the ESQL interface directly, then
the migration contains more steps, as follows:
1. The function sqldynopen() has been replaced with a series of functions:
sqldynprep() - to PREPARE a statement
sqldynsetn() - to associate a cursor name with a query
sqldyndesc() - to retrieve column attribute definitions
sqldynexec() - to EXECUTE a statement
2. The parameter list for sqlcdbind() has been changed to add another
parameter for the SQLSTATE value.
3. ALL ESQL functions will now return control to the application -
including sqllogout().
4. The functions sqlrtnmem(), sqlprepd() and sqlnprepd() have been
removed.
5. The name of the C header file, sqlhli.h, has been changed to proesql.h.
6. The exit() function is no longer redefined to call sqllogout() - it
will now function as described in the C runtime library. The function
sqllogout() no longer causes image exit.
7. The argument list for sqlfetch() (Static FETCH), sqlupdrow()
(Static Positioned UPDATE) and sqlrequest() (Static EXECUTE)
8. The sqlclose() function has been replaced by sqldynclose().
===========================
9. REMOTE DATASERVER ISSUES
===========================
See the hard-copy release note for information on issues concerning
dataservers.
======================
10. R-CODE PORTABILITY
======================
One of the new Version 7 capabilities addresses the
need for developers to recompile their applications on
each target platform (for example, different chip architecture
and operating system) to which they want to port their
application. Version 7 makes it possible to build and compile
a single version of an application, then run it unchanged
- without recompiling - on any PROGRESS-supported platform
if porting between the same windowing systems (for example,
Motif to Motif).
In the current Version 7 release, a problem exists which
can prevent PROGRESS r-code from being totally portable.
When taking PROGRESS r-code from one platform to another,
you might encounter problems if the machine to which you
are porting has a different byte-ordering than the platform
where the r-code was compiled (for example, from a 386/486
machine to a 88000-based platform).
The problem is not absolute. In most cases, r-code
compiled on one machine runs with no changes on any other
platform, regardless of chip architecture or operating
system. However, if you use certain combinations of 4GL
instructions, the PROGRESS Compiler can generate
non-portable r-code.
A future edition of the "PROGRESS Version 7 Technical
Bulletin" will include plans for the next release in which
this problem will be fixed.
12.B Networking
----------------
* NOVELL SPX CLIENTS TO NLM SERVER
Novell continues to update support files for MS-Windows and the
IPX/SPX protocol. The latest set of these files addresses a problem
described by Novell as "the black screen of death syndrome," where the
screen goes black with only a cursor in the upper-left corner.
This occurs only when running applications that use SPX, such as a
PROGRESS V7 client connected to a PROGRESS NLM database server over
SPX. Novell and PROGRESS strongly suggest the latest support files
for Windows and IPX/SPX be used to address this problem and those
with similar symptoms and to provide overall SPX stability.
To use the latest release of these files, you must use the ODI
implementation of IPX. Obtain and install the following files,
which can be acquired either from your local Novell reseller or
via the NOVFILES forum on CompuServe accessible via "GO NOVFILES":
DOSUP9.EXE
WINUP9.EXE
If Windows is running in standard mode, load the TBMI2.COM TSR
prior to starting Windows.
If Windows is being run in 386 Enhanced mode, verify that the
SYSTEM.INI file has the following line in the [386Enh] section:
network=*vnetbios,vnetware.386,vipx.386
Running a non-Windows application, opening a DOS session, or
executing a DOS command via DOS, DOS SILENT, or OS-COMMAND
4GL statements might cause loss of an SPX connection if the proper
versions of NetWare for Windows support files are not being used.
* PATHWAY ACCESS WOLLONGONG TCP/IP v3.0 NOT SUPPORTED
Pathway Access Wollongong TCP/IP v3.0 is not supported in this
release.
* SOCKET USE WITH PC CONNECTIONS TO UNIX USING PATHWAY
If you repeatedly disconnect then reconnect databases using the
Pathway Wollongong 2.1.1 WINSOCK product, sockets are not closed
and eventually PROGRESS is unable to reestablish connection due
to no sockets being available.
* SPX CLIENTS TO NLM SERVER
When running more than two SPX clients to an NLM server, client hangs
might occur. The client screen freezes for the hung clients, and
attempts to kill them via their user numbers hang the rconsole
screen for the server session. Rebooting the client PC does not unhang
the rconsole.
* TCP AND SPX CLIENTS TO NLM SERVER
Connecting to an NLM server from a PC with either a TCP or SPX client
might result in a client disconnect. The following error message appears:
Error reading socket, ret=-1, errno=2. (778)
* SPX CLIENTS TO NLM SERVER
When multiple SPX clients are connected to a single NLM server, and the
clients disconnect using <CTRL>-<BREAK> or, if present, the Record-Lock
alert box, some but not all properly complete the disconnect, with
the remaining client(s) inert. Attempting a "kill" results in a
message that the user is being disconnected, but following transaction
backout both the NLM server and the PC are hung. To unhang the
console, an "unload _MPROSRV" command is necessary; unhanging the PC
requires rebooting.
* CLIENT TO ANY DATASERVER
You must always shut down a MS-Windows client properly when
connected to a DATASERVER. If a remote client abnormally
terminates, the client process remains on the remote machine
and must be manually terminated.
* DDE SERVER DOES NOT RECOGNIZE "PROCESS EVENTS"
If you connect to a database with a a DDE server, PROGRESS
does not properly execute a PROCESS EVENTS statement. PROGRESS
might not recognize and process events.
Workaround: Connect to the database with another protocol
or in single-user mode.
12.C User Interface/Widgets
-----------------------------
* OUTPUT TO PRINTER NOT WORKING CORRECTLY WITH EDITOR WIDGETS
The OUTPUT TO PRINTER statement drops characters for EDITOR widgets
that use the INNER-LINES INNER-CHARS syntax.
* CURSOR-OFFSET ATTRIBUTE OF FILL-INS AND EDITORS
Implementation of the CURSOR-OFFSET attribute differs
between fill-in field and editor widgets. PROGRESS assigns
a value to the attribute when you leave the fill-in field
widget, whereas it assigns the value when you enter the
editor widget. As a result, fill-in field widgets do not
allow entry at the position where you click the mouse;
editor widgets allow entry at the precise location of the
mouse-click.
* SELECTION LIST
If you set the DRAG-ENABLED attribute for a selection
list to NO while the MULTIPLE attribute is set to YES,
PROGRESS generates a VALUE-CHANGED event when you use
the scrollbar.
* FAILURE OF :LOAD-IMAGE() METHOD DOES NOT SET ERROR STATUS
If the :LOAD-IMAGE() method fails, ERROR-STATUS:ERROR
is not set regardless of whether NO-ERROR is specified.
The logical variable associated with the method is also
not set to NO, but is set to ? regardless of its previous
contents. To determine whether the :LOAD-IMAGE() method
has successfully completed, query the logical variable
used with it in the 4GL statement. A zero value will denote
that the method was successful.
* 3-D EDITOR AND FILL-INS DO NOT TURN GRAY WHEN MADE INSENSITIVE
The color of an editor or fill-in widget does not turn gray when
it is made insensitive.
12.D ADE
---------
* NO WARNING IF PROGRESS.INI FILE HAS NO WRITE PERMISSIONS
If the PROGRESS.INI file is not writable, PROGRESS does
not save any changes you made to fonts or colors, and it
does not generate warning messages stating that the save
will not take place when you exit the session.
* MULTIPLE CTRL-BREAKS (R-175)
While running a procedure in the Procedure Editor, multiple
CTRL-BREAK, cause the Editor pull-down menus to disappear.
12.E User Interface Builder
----------------------------
* BOGUS FRAME-SELECT-UP ERROR WHEN ADDING FIELDS FROM SELECTED TABLE
The error message "**´frame-select-up´ was not found. (293)" displays
when xadding fields from the last displayed table in the "Tables:" column
in the Table Selector dialog box, if the table used is the last
visible table in the list. It goes away after the first few times the
table is used.
* SLIDER COLOR
To change the color of a slider, you might have to invoke
the Property Sheet twice, for two different attributes:
the first time to select the new color, the second time
to change the widget WIDTH. PROGRESS might not display your
requested change in color until you leave the Property
Sheet the second time.
* TRIGGER-DELETE-CANCEL STILL DELETES CODE (R-136)
Using the Section Editor on any widget, if you select some code and
then use the Trigger Delete button, the code is deleted even
if you select Cancel to leave the Section Editor.
* TOGGLE BOX LABELS WHEN ASSOCIATED WITH DATABASE FIELDS
If you override the Data Dictionary label of a field that is represented
using a toggle box widget, upon making a change the UIB will show it
on the design window but will revert to the Dictionary label when
creating and running the 4GL.
* NAVIGATION TEMPLATE ERRORS WITH C-ISAM
When using the template navuprec.w with C-ISAM, the following error
might result:
STOP recid function not supported for this table (552)
You will still be able to use the template correctly.
* NAVIGATION TEMPLATE WITH SYBASE DATABASE
While developing with the UIB, if you create a new record using
the Navigation Template then delete that same record, an error
may result which exits you from the UIB. Upon trying to restart
the UIB PROGRESS may generate a General Protection Fault.
* CREATING AND STORING SYBASE RECORDS USING NAVIGATION TEMPLATE
When creating and storing SYBASE database records using the
Navigation Template, the new records are not seen until you rerun
the procedure.
* CREATING THEN DELETING SYBASE RECORDS USING NAVIGATION TEMPLATE
If you create a SYBASE database record using the Navigation Template
then attempt to delete the new record, the following error results:
"Wrong record ID.(2091)"
"Record was modified by another program or by a trigger.(2092)"
* CREATING AND STORING ORACLE RECORDS USING THE NAVIGATION TEMPLATE
While developing with the UIB, if you select some fields associated
with an ORACLE database and use them with the Navigation Template,
after creating and storing a new record the following error occurs:
"<tablename> record was changed since you have read it(1071)"
"Unable to update <fieldname> Field.(142)"
* CREATING AND STORING ORACLE RECORDS USING THE NAVIGATION TEMPLATE
When creating and storing new records on an ORACLE database using
the Navigation Template, adding multiple records might result in
some of the records not being created.
* UPDATING ORACLE DATABASE RECORDS USING THE NAVIGATION TEMPLATE
When updating an ORACLE database record using the Navigation Template,
the data may have to be updated twice.
12.F Language
--------------
* DOS SILENT RETURNS FOCUS TO WRONG WINDOW
Focus is returned to the wrong window following a DOS SILENT
command, if you realize more than one window created by the
PROGRESS application.
* MISSING "}" CAUSES ERRONEOUS ERROR MESSAGE (R-152)
Using a parenthesis ()) instead of a brace (}) in an include
file reference generates the following erroneous error message.
Preprocessor expansion buffer overflow (2939)
* COMPILE LISTING INCORRECT FOR INCLUDE FILES
COMPILE LISTING can sometimes generate errors when dealing with nested
include files. The include file parameters might not be displayed in
an expanded state, and the numbering scheme for the lines of source
code might also become confused.
* NUM-COPIES NOT FOR USE WITH SYSTEM-DIALOG PRINTER-SETUP
The NUM-COPIES keyword is used only with the OSPRINT procedure,
although current documentation implies that it can be used with
SYSTEM-DIALOG PRINTER-SETUP.
* SQLCODE OF 100 GENERATED WITH "CREATE" AND "WRITE" TRIGGERS
If you have a CREATE or WRITE trigger which consists only of a
MESSAGE statement, inserting or updating from SQL will result in
an SQLCODE of 100 even when the statement has completed successfully.
The appropriate code is 0.
12.G Procedure Editor
----------------------
* UNABLE TO CHANGE FONT USING KEYBOARD
The default font or buffer font can be changed only by using the
mouse pointer to bring focus to the numbered font.
12.H Librarian
---------------
* CANNOT CHANGE ITEM DESCRIPTION
When you edit an item supplied with the installed version
of the Librarian, if you try to save your edits, PROGRESS
generates an error message: "Could not save description file
<filename>.dsc." When you dismiss the error message, PROGRESS
returns to the main window. It saves any changes except
for the new item description.
12.I Data Dictionary
---------------------
* CORRUPT .d FILES NOT DETECTED DURING LOAD VIA DICTIONARY
If you have a .d file that contains bad data, and you
load this file to your database interactively using the Data
Dictionary, the Dictionary reports a successful load with
zero errors and writes the corrupt data to your database. This
happens regardless of the level of error detection you
select.
Although this problem only occurs with .d files containing
corrupt data, as a safeguard you should load .d files to your
database using PROUTIL bulkload only.
* WRITING AND COMPILING DB TRIGGER-CODE LEADS TO RECOMPILE
If you write, compile, and save a database trigger procedure,
when you register the trigger in the Dictionary, PROGRESS
generates the following error message:
Compile aborted. Save not specified and r-code file
exists... (468)
* DELETING PRIMARY INDEX CAN UNDO ENTIRE DICTIONARY TRANSACTION
If you delete the primary index in the Data Dictionary by first
renaming it, creating a new index as primary, then deleting the
original renamed primary, the entire transaction might be undone
upon exiting the Dictionary.
12.J Data Administration
-------------------------
* DROPPED TABLE VERIFIED ERROR (R-181)
An error can occur when verifying an ORACLE table definition after an
ORACLE table has been dropped.
* SPX CONNECT/DISCONNECT HANGS DATA ADMINISTRATION (R-171)
Using the Data Administration tool to connect and then disconnect an
NLM database via SPX causes the Data Administration tool to hang. The
menus and submenus are active but do not work. The Data Administration
window also does not close using the task list or ALT-F4. Non-PROGRESS
applications can be accessed and MS-Windows can be shut down. If TCP/IP
is used to connect to the NLM database this does not occur.
* BULKLOADER AND SYBASE DATASERVER
When you create a Bulkloader file from the Data Dictionary and select *
for all files, they all might not be highlighted. You might have to
select all the files manually.
* SYBASE HIDDEN TABLES
When showing the hidden table PROC-TEXT-BUFFER with SYBASE data
definitions, the following errors might result:
STOP ** find FIRST/LAST failed for table sybase_users (565)
* SYBASE HIDDEN TABLES
When verifying SYBASE table definitions, you may receive error
565 when choosing the following tables: sybase_columns,
sybase_comments, sybase_keys, sybase_logins, sybase_objects.
* VERIFYING SYBASE TABLE DEFINITIONS
Verifying SYBASE table definitions created from types.sql gives
the following errors:
i null value (mandatory) mismatch.
b null value (mandatory) mismatch.
b-1 extra field on progress side.
* CONNECTING ADDITIONAL SYBASE DATABASE
If a working database is already selected and you select an additional
SYBASE database, the first database is no longer selected when going
into Database Administration. You have to go back to the Data
Dictionary and reselect the first working database.
* SECURITY ON C-ISAM SCHEMA HOLDER
If you disallow the blank user on a C-ISAM schema holder, the blank
user is still able to Add/Update a new C-ISAM table.
* DISPLAYING C-ISAM RECORD LAYOUT
An error might be generated in trying to display a C-ISAM record
layout:
STOP ERROR ** unable to realize editor widget edit_widg (4025)
* SQL ARRAY INDICATOR "##" MAY BE DISALLOWED ON CERTAIN PLATFORMS
The PRO/SQL "Dump as CREATE TABLE Statement..." uses an
array indicator of "##" which is not allowed for table or field names
on certain SQL engines.
* SQL TABLE AND FIELD NAMES CREATED USING HYPHENS ONLY
The PRO/SQL "Dump as CREATE TABLE Statement..." uses the
hyphen character in generating SQL DLL statements. The hyphen
might not be recognized on other SQL engines as an allowable character
in table and field names.
* BOOLEAN PARAMETERS CANNOT BE PASSED TO OR FROM ORACLE STORED PROCS
Parameters declared as BOOLEAN cannot be passed as arguments to or
from ORACLE stored procedures. Workaround: declare the parameters
as type INTEGER and pass the value 0 for FALSE and 1 for TRUE.
datatype in the schema holder can be changed to LOGICAL and
the format to yes
o or true/false.
* ORACLE ERROR -6502 FOR varchar2 ITEMS LONGER THAN 255 CHARACTERS
ORACLE will return an error if you define a varchar2 item longer
than 255 characters.
12.K Application Compiler
--------------------------
* COMPILER TOOL BUILDS "SAVE INTO" PATH INCORRECTLY
If you specify "Save into" in the Compiler to keep
R-code separate from source, and you name the "Save into"
directory with a complete path designation rather than
a relative path, the Compiler tries to save r-code
into a new directory name created by appending the "Save
into" pathname to the source directory pathname.
If this pathname created by the Compiler should
not exist, PROGRESS generates an error stating that it
"cannot write to <directory>". If the pathname is for
an existing directory, PROGRESS stores the r-code there
rather than in the intended directory.
Workaround: Name the "Save into" directory using relative
path designations. For example, "../appdir/r-dir".
12.L Translation Manager
-------------------------
* MENUS NOT LOCKED WHEN RUNNING DATA DICTIONARY
If you use the Translation Manager to open the Data
Dictionary, the TranMan menus are not dimmed, and you can
pull them down. If you then try to run another tool, PROGRESS
generates the following error message:
"_RunTool" was not found (293)
* ACQUIRING STRINGS OR APPLICATION COMPILE MIGHT HANG THE PC
When acquiring strings through Translation Manager, Translation
Manager might hang after loading a certain number of strings.
Work will resume if any of the Translation Manager keys are pressed.
This also might happen during an application update, in which
the Translation Manager compiles all procedures that were
updated.
12.M Utilities
---------------
* PROUTIL WILL NOT WORK WITH USER-DEFINED SORT ROUTINES ON NLM
On NLM only, PROUTIL will not work with user-defined sort routines.
* PROLIB NOT HANDLING CODE PAGES CONSISTENTLY
PROLIB stores filenames in an unspecified code page. It is possible
to add filenames in one code page and later add additional filenames
in another code page. If the files contain 8-bit characters,
the resulting mix of code page files can result in an inability
to retrieve files accurately.
12.N ESQL/C
------------
* DEFAULT CLAUSE DOES NOT SUPPORT SPECIAL VALUES "USER" AND "NULL"
If you use a statement in the following format, it does
not pass syntax check:
CREATE TABLE mytable
(c1 CHAR DEFAULT USER,
c2 INT DEFAULT NULL).
* SQLCPP - NO NETWORK CONNECT ON WINDOWS (R-153)
Version 7.3A does not support SQLCPP connections to remote databases
because the prorpc module (which enables a protected mode image to
talk with real mode images) is not included in Version 7.
* LOCK CALLBACK FUNCTIONS NOT CALLED FOR ESQL/C SEARCHED UPDATE/DELETE
If one user has a record locked (either 4GL or ESQL) and a
second user first sets a lock callback function (by calling
sqlsetlogoption(ESQL_LOCKFUNC, ...) and then attempts a searched
UPDATE or DELETE (update customer set name="FOO") on the locked
table, the lock callback function isn´t called (as it is for
cursor operations).
* ESQL PREPROCESSOR PERFORMANCE ON MS-WINDOWS vs. UNIX
When using the ESQL preprocessor, there are now differences
in the way it works on Unix and MS-Windows. UNIX and MS-Windows
treat SQLCPP differently when a file can´t write to its .c file.
12.O Internationalization
--------------------------
* NOT SPECIFYING -xc (-cpcoll) AT STARTUP MAY CAUSE STARTUP FAILURE
When using a database with its own collation table, if the convmap.cp
does not contain a collation table called "basic" for the given
-charset, connection might fail. Always use the -xc (-cpcoll)
startup parameter to designate the collation table to use
if it is different from "basic". This is true even if no database
is connected. "Basic" is the default.
* LOADING 7.2 DEFS INTO EMPTY 7.3 DATABASE DIRECTS INDEX REBUILD
When you load Version 7.2 DF files into an empty Version 7.3 database
PROGRESS returns a message that the data in the database differs from the
.df loaded. You will be instructed to do an index rebuild.
* UIB TOO BIG FOR RUSSIAN MS-WINDOWS
When running Russian MS-Windows, UIB windows are too big for the
screen due to the increased width of Cyrillic fonts. A font
sized 24x7 should be used, for example fonts from CYRWIN.
* PROLIB NOT HANDLING CODE PAGES CONSISTENTLY
PROLIB stores filenames in an unspecified code page. It is possible
to add filenames in one code page and later add additional filenames
in another code page. If the files contain 8-bit characters,
the resulting mix of code page files can result in an inability
to retrieve files accurately.
12.P Portable R-code
---------------------
* CRC PROBLEMS WITH TRIGGER-CODE DEPLOYMENT
If you deploy trigger procedures as r-code with CRC
enabled, you encounter discrepancies between the CRC of
the _file-trig file and that of the new trigger r-code.
There are two workarounds for this issue:
- Provide incremental DF files with new trigger code.
- In the Data Dictionary, invoke the trigger code
dialog box for the affected table or field. Then
choose "Save". The CRC is recalculated and stored.
12.Q PROBUILD
--------------
* PROBUILD REQUIRES DDE FOR LINK SCRIPT AND PROPER BUILD
When probuilding a new MS-Windows executable, you must select DDE
in order for the link script and the build to proceed properly.
* CODE ADDED TO LIBRARY WITH CAPITALS
If you create a library of trigger code under MS-Windows that does no
screen interaction and then port this library to UNIX, PROBUILD cannot
find the files because DOS capitalizes the file names and UNIX looks
for file "A.P" rather than "a.p".
12.R DataServers
-----------------
* PROTOORA.P MISNAMES "VIEW BUFFER" TABLE
PROTOORA.P will misname a "view buffer" table by appending "BUFFER_"
at the front of the name.
* ADDING DESC INDEXES TO ORACLE SCHEMA IN THE DATA DICTIONARY
Adding a desc index to a table with the Data Dictionary after having
already accessed the table, then executing a USE-INDEX on the new desc
index in a procedure, causes a system error similar to the following:
SYSTEM ERROR: orextract_idx Index 6 is not in cache (2727)
* PROGRESS/400 DataServer
If you use PROGRESS/400 you must upgrade your DataServer to 6.2M09
to use Version 7.3A clients.
* CISAM: PC CONNECTION TO UNIX WITH BINARY ISAM TYPE
When connecting from a PC to a UNIX server and creating a binary
ISAM type in a field, unexpected data may appear.
* C-ISAM STRINGS LONGER THAN FIELD LENGTH NOT TRUNCATED
PROGRESS does not properly truncate strings longer than the length
of a field, and instead issues an error message without updating
the field.
* C-ISAM "MULTI-SEGMENTED KEYS" SUPPORTED BUT NOT DOCUMENTED
Multi-segmented keys are supported on C-ISAM but are not
yet documented.
* C-ISAM "OVERLAYED FIELDS" SUPPORTED BUT NOT DOCUMENTED
C-ISAM "overlayed fields" are supported but are not
yet documented.
* ORACLE: CANNOT SELECT ROWS USING DATE
Use the ORACLE TRUNC function when testing a date parameter for
equality with a column in the stored procedure.
For example, in the ORACLE stored procedure say:
select ... from <table> WHERE TRUNC (<column>) =
TRUNC (<parameter>
Instead of:
WHERE <column> = <parameter>)
12.S RESULTS
-------------
* ERROR MESSAGE WHEN USING COUNTER ON ALL SECTIONS
When creating a "counter" calculated field for all sections,
PROGRESS gives the following error message twice:
**qbf-section record not on file. (138)
The counter field will be created correctly, and the correct
output will be generated.
* DATABASE ALIASES FOR MORE THAN ONE DATABASE
When an alias (or aliases) is created for one database and then a
second is connected, the alias(es) is related only to the first
database and not to the second. The alias´ parent table will be
related to the correct tables in both databases. To get proper
relationships, remove and then recreate the aliases with BOTH
databases connected at the same time.
* PRINTING LABEL WITH PRINT-PREVIEW ON C-ISAM
Trying to print a label from the print-preview feature using a C-ISAM
database generates the error:
STOP Could not load dll procedure PROPRINT.DLL (3258)
* STARTING RESULTS WITH REPORT BUILDER GIVES SHARING VIOLATION
When you start the Report Builder from the ADE desktop, then start
RESULTS during the same session, you may get a sharing violation or
an lseek or lwrite error when you enter or exit RESULTS. Or,
you might experience poor performance under these conditions.
The problem occurs when Report Builder attempts to use a READ-ONLY
PROGRESS.INI file.
* PREVIEW/PRINT ALIGNMENT INCORRECT DEPENDING ON NATIVE FONT
Depending on the characteristics of the native font, a Preview or
Print may result in misaligned columns. The workaround is to choose
a display driver in MS-Windows which uses a monospaced font, or
edit the PROGRESS.INI file and change font 0 to use a monospace
font.
* RESULTS TOOLBAR DOES NOT DISPLAY IN JAPANESE MS-WINDOWS
The RESULTS Toolbar does not display in Japanese MS-Windows. To
use the Report, Export, and Label layouts the user should set RESULTS
to turn off the Toolbar even though it is not actually displayed.
This is done by going into the View menu and creating a Browse
Browse Query, then selecting View and toggling the Toolbar.
* DELETION OF NON-NATURAL JOINS
When you create a non-natural join, if you delete the WHERE
relationship it will not stay deleted unless you do so immediately
by way of an UNDO, or if you remove the table relationship
completely then re-establish it.
12.T Report Builder
--------------------
* STARTING RESULTS CONCURRENT WITH REPORT BUILDER GIVES MEM VIOLATION
When you start the Report Builder from the ADE desktop, then start
RESULTS during the same session, you may get a sharing violation or
an lseek or lwrite error when you enter or exit RESULTS. Or,
you might experience poor performance under these conditions.
The problem occurs as Report Builder attempts to use a READ-ONLY
PROGRESS.INI file.
* DATABASE TRIGGERS MUST BE COMPILED WHEN USED WITH REPORT BUILDER
If you have database triggers and plan to use Report Builder, all
trigger procedures must be compiled R-code. If you try to run
Report Builder with uncompiled P-code, it will return 0 records.
* CANNOT OVERRIDE CERTAIN CONNECTION PARAMETERS WITH REPORT BUILDER
When trying to override saved connection information using the
Runtime Report Engine RB-DB connection parameter, the connection
string is parsed to look only at specific parameters. All
others are ignored. This means that it is not possible to
override parameters such as database type and schema holder.
The parameters acknowledged by Report Builder are -H, -S,
-DB, -N, -U, and -P.
* REPORT BUILDER DOES NOT SUPPORT OUTER JOINS
Report Builder currently does not support outer joins.
* REPORT BUILDER DOES NOT SUPPORT MULTI-DATABASE CONNECTIVITY
Report Builder currently does not support multi-database connections.
* SORTING OF CHARACTERS 128 AND ABOVE
For sorts processed locally by Report Builder (sorts on aggregate
fields and some calculated field expressions) character values are
sorted according to their numeric values in the Windows code page,
rather than the expected collation sequence. Sorts on data fields
and calculated field expressions evaluated by the database server
are processed using the expected collation sequence.
Progress Software Technical Support Note # 13812