=======================================================
RELEASE NOTES
FOR
INFORMIX DYNAMIC 4GL COMPILER 3.10.UC1 (3.10.1i)
DATE: 2000/12/01
=======================================================
TABLE OF CONTENTS
1.RELEASE NOTES OVERVIEW
2.MIGRATION ISSUES
3.ENHANCEMENTS AND MODIFICATIONS
4.BUG CORRECTION LIST
1.RELEASE NOTES OVERVIEW
===============================================================================
The purpose of these release notes is to briefly inform users of enhancements
and modifications in the features supported by this product in relation to
its earlier versions.
This document is not intended to be all-inclusive, but rather to assist you
in the upgrade process. Please consult the product manuals and supplements
for additional information on product features and product behavior.
2.MIGRATION ISSUES
===============================================================================
The new name of the Four J's Universal Compiler is :
'Four J's Business Development Language Compiler'
a.k.a 'Four J's BDL Compiler'.
When migrating from version 3.xx to 3.10, it is mandatory to recompile all
4GL sources and forms.
3.ENHANCEMENTS AND MODIFICATIONS
===============================================================================
Version 3.10.1i
-------------------------------------------------------------------------------
* 4GL Debugger.
This version includes a debugger. For more details, read the DEBUGGER file
provided in the FGLDIR/release directory.
* Open Database Interface support.
This version includes the libdbgen library to create runners supporting
the Open Database Interface extension.
* Support for ASCII terminals (FGLGUI=0) on MS-Windows Systems.
Warning! The default value is still FGLGUI=1 on this system.
* Support for variable parameters in C functions.
The compiler has a new compilation option '-z myfuncs.out
$ fgl2p -z myfuncs.out -o myprog.42r module.4gl
* Application termination on MS-Windows Systems
The instruction "OPTIONS ON TERMINATE SIGNAL CALL " defines a function
to be called when an application terminates.
On Windows, this function will be called in following cases:
- You close the console window the 4GL program has been started from.
- You terminate the current user session (log off).
- You shutdown the system.
* Support of WTK Version 2
Warning! You must install fgl2c.res4 and fgl2c.tcl4 in $FGLDIR/etc to
enable this version.
Read release notes of WTK Version 2 for more details.
Verison 3.04.7c
-------------------------------------------------------------------------------
* Thai character set support.
To use this feature, you must do the following:
- check that you have install a INFORMIX-GLS version with Thai support.
- link a runner with GLS (Global language Support) library.
- set CLIENT_LOCALE to "th_th.thai"
Verison 3.04.7b
-------------------------------------------------------------------------------
* 4GL Debugger.
see in Version 3.10.1g
* Multi-database CONSTRUCT.
The 4GL CONSTRUCT instruction now generates database specific SQL syntax
instead of pure Informix SQL syntax. For example, numbers are no longer
generated as string constants, the LIKE predicate is generated instead
of MATCHES when the user enters * ? wildcard characters and SQL Directives
are produced for special data types such as DATEs. You must configure the
SQL Directives in fglprofile to translate the generated directives produced
by the CONSTRUCT instruction.
See the Open Database Interface documentation for more details.
* String literals in SQL.
The single quoted strings in static SQL statements are no longer converted
to double quoted string literals before sending to the database server.
The double quoted string literals in SQL statements are now automatically
converted to single quoted strings for ANSI SQL conformance. This applies
to all kind of SQL statements (static, dynamic and written in SQL Blocks).
* Multi-database fglschema tool.
A new database schema extractor is provided to create '*.sch' files from
non-Informix databases. The name of this tool is fgldbsch and the source
code is in FGLDIR/src.
* TCL interface: fgl_winbutton now produces a dialog with a Windows look
& feel. New bitmaps (information, exclamation, question, stop) are provided
with the new WTK server.
* Interruption is now well supported on Windows platforms. This includes
4GL program flow interruption and SQL interruption. For more details,
see the OPTIONS instruction using the SQL INTERRUPT ON/OFF clause.
Version 3.02.1b
-------------------------------------------------------------------------------
* Product extension control.
A special licence is required to use product extensions such as the Open
Database Interface, current licences will not work. Please contact your
Support Center for a new licence.
Version 3.02.1a
-------------------------------------------------------------------------------
* Open Database Interface support.
This version includes the libdbgen library to create runners supporting
the Open Database Interface extension.
See ODI extension documentation for more details.
Version 3.00.2b
-------------------------------------------------------------------------------
* Support of Informix 2.10 :
Informix ESQL/C 2.10 is now supported. An extra library has been added
(libix210.a) and the tools fglmkrun, fgl2c and fglschema have been changed
to support this new library.
Version 3.00.1n
-------------------------------------------------------------------------------
* P-code link optimization flag.
Prior to version 3.00, the P code executable generated by the 4GL linker
"fgllink" was optimised. The resulting .42r executable file was only
referencing used 4GL functions, discarding unused ones. The major problem
of this optimisation was that the 4GL linker was also discarding 4GL
functions called only from C functions. This behavior was leading to
the following error at execution time, when the call to the 4GL function
was issued by the C function:
ERROR(-1338):The function '' has not been defined in any
module in the program.
From version 3.00, the 4GL linker includes references to all 4GL
functions defined in the 4GL modules linked together. This can dramatically
increase the size of the resulting 4GL P code executable in some cases,
but avoid the run time error.
You can enable the linking optimization by adding the -O ( an uppercase
letter O and not the number zero ) to the link line of your 4GL application.
To prevent the 4GL P code linker removing functions only called in C
functions and never called from 4GL modules, you can add a special 4GL
function containing calls to the 4gl functions used by the C modules.
Version 3.00.1m
-------------------------------------------------------------------------------
* fglschema behavior:
Version 3.00.1f of fglschema handles new Informix Universal Server data
types in the following way:
- BOOLEAN, INT8 and SERIAL8 can be converted to CHAR(1) and DECIMAL(19,0)
respectively when using fglschema with the "-c" flag.
- ROW, LIST, MULTISET and SET types are not supported.
When fglschema detects an unsupported data type, a warning is displayed
and by default the table definition is not written to the schema file.
This is mandatory to get compilation errors when using "DEFINE LIKE"
instructions as follows :
RECORD LIKE or SELECT *
However, you can use the "-r" flag to force fglschema to write the table
definition without the columns created with unsupported data types.
Run fglschema with the "-h" option for more details.
* 4GL BOOLEAN and database BOOLEAN:
4GL uses the INTEGER data type for boolean expressions. INFORMIX Universal
Server introduces a new BOOLEAN data type which is actually CHAR(1) where
the "t" and "f" values represent the TRUE and FALSE boolean values. These
"BOOLEAN" values cannot be used directly in 4GL boolean expressions.
Here is an example of 4GL code that raises a data type conversion error :
# Prerequisite : The database holds a table defined as :
# CREATE TABLE tab1 ( col1 BOOLEAN )
#
DATABASE stores
MAIN
DEFINE vbool INTEGER
LET vbool = ( 1 = 0 )
INSERT INTO tab1 VALUES( vbool )
END MAIN
-9634 No such cast.
The specified cast does not exist. Use the CREATE CAST
statement to define the cast.
The following functions are provided to convert INFORMIX Universal Server
"BOOLEAN" values to 4GL INTEGER booleans:
fgl_charbool_to_intbool Converts an Informix Universal Server BOOLEAN
value ("t", "f") to a 4GL INTEGER value (TRUE,
FALSE). The function returns NULL If the given
value does not match "T", "t", "F" or "f".
fgl_intbool_to_charbool Converts a 4GL INTEGER value to a CHAR(1) value
to be stored in a BOOLEAN column of an Informix
Universal Server table. The function returns NULL
if the given value is NULL.
The above example can be written as follows:
# Prerequisite : The database holds a table defined as :
# CREATE TABLE tab1 ( col1 BOOLEAN )
#
DATABASE stores
MAIN
DEFINE vbool CHAR(1)
LET vbool = fgl_intbool_to_charbool( 1 = 0 )
INSERT INTO tab1 VALUES( vbool )
END MAIN
On the other hand, when you retrieve a BOOLEAN values from the database,
you can convert that value with the fgl_charbool_to_intbool( ) as in the
following example :
# Prerequisite : The database holds a table defined as :
# CREATE TABLE tab1 ( col1 BOOLEAN )
# and fglschema has been executed with the "-c" flag.
#
DATABASE stores
MAIN
DEFINE rtab1 RECORD LIKE tab1.*
SELECT * INTO rtab1.* FROM tab1
IF fgl_charbool_to_intbool( rtab1.col1 ) THEN
DISPLAY "TRUE"
ELSE
DISPLAY "FALSE"
END IF
END MAIN
Version 3.00.1k
-------------------------------------------------------------------------------
* Environment variable interpretation has changed on N.T :
It appears that several environment variables cannot be retrieved by the
Four J's Dynamic Virtual Machine and by the Four J's Universal Compiler.
This problem is due to Informix GLS version 3.0 API functions and to
our internal initialization function. The following environment
variables cannot be managed by the Four J's Dynamic Virtual Machine and
by the Four J's Universal Compiler:
- DBDATE
- DB_LOCALE
- DBCENTURY
- DBMONEY
- DBFORMAT
- CLIENT_LOCALE
- INFORMIXDIR
- SERVER_LOCALE
Instead of setting those variables in the fglprofile file, please set them
directly in the environment using the command 'set'.
Example:
C:\> set INFORMIXDIR=C:\informix
C:\> set DBDATE=DMY4/
* Network traffic optimization : The number of IP packets being exchanged
between runner and frontend has been reduced.
Version 3.00.1e ( Compatibility level : Informix 4GL 7.30 )
-------------------------------------------------------------------------------
Four J's Universal Compiler 3.00 offers new features that are not available
in earlier releases. More about these features can be found in the Four J's
Universal Compiler User Guide.
* Java Client
Allows for the display of D4GL applications in Web browsers with little or
no recoding. Users download a Java applet that is basically like the WTK
written in Java. This applet controls display logic much like the WTK does;
Application logic is still performed on the application server.
* Global Language Support (GLS)
GLS enables internationalized products written in 4GL, as described in the
Global Language Support Guide.
NOTE: The HTML Client and X11 Client will not support all languages in the
initial release.
* Local Editing
By default, every keystroke generates a network roundtrip between the
graphical client and the application server. Enabling local editing allows
the client to send typed characters to the application server when leaving
the field only. This reduces network traffic.
* Cut & Paste
This feature enables the standard Cut & Paste functionality within a Four
J's Universal 4GL Windows session.
* Folder Tabs
This feature permits the creation of Windows-like folder tabs, enabling the
user to navigate easily between multiple screens.
* Window close control
It is now possible to control the behavior of a 4GL application when the
user closes the main window on the client workstation. Several options are
provided as stop, continue, call a function.
* Dynamic report configuration
4GL reports are now configurable at runtime (for example, the page size can
be specified during the program execution).
Here is the new syntax of the START REPORT instruction :
START REPORT
[TO {
SCREEN |
PRINTER |
FILE {"file"|} |
{"file"|} |
PIPE {"program"|} |
OUTPUT {""|} [DESTINATION {""|}]
}
]
[WITH {
TOP OF PAGE = |
PAGE LENGTH = n |
TOP MARGIN = n |
BOTTOM MARGIN = n |
LEFT MARGIN = n |
RIGHT MARGIN = n |
[, ...]
}
]
Where can be one of the following: "SCREEN", "PRINTER", "FILE", "PIPE".
Those values are NOT case-sensitive.
Example:
START REPORT repname
TO OUTPUT string1 DESTINATION string2
WITH TOP MARGIN = 2,
TOP OF PAGE = "^L",
PAGE LENGTH = pglen
If the WITH clause appears, the explicitly stated parameters override the
corresponding parameters explicitly stated in the OUTPUT section of the
REPORT function or those implied by the defaults. Note in particular that
any report can now use either top-of-page character string processing or
repeated blank lines to space to the page, depending on attributes set when
the report is started.
* Concatenation operator
The SQL standard '||' concatenation operator can now be used in 4GL. This is
very useful because it is a real operator, for example :
CALL open_file( mycharvar || '.txt' )
* SQL Blocks
SQL blocks can hold SQL statements that do not follow the SQL 4.10 grammar.
All new INFORMIX SQL 7.x statements that can be prepared are now supported
SQL blocks are delimited by the "SQL" and "END SQL" keywords. They can be
used as a static SQL statement or to declare a cursor.
Host variables and target (into) variables must be prefixed by the dollar.
Some 4GL-SQL extensions like the "THRU" keyword and the start character are
fully supported inside SQL blocks.
Example :
SQL
SELECT emp.name, emp.salary, emp.address
INTO $r_emp[n].name,
$r_emp[n].salary,
$r_emp[n].address
FROM employee
WHERE empno = $empno
END SQL
* New SQL instructions
- EXECUTE IMMEDIATE {"stmt"|variable}
Executes a statement directly without any host or target variable.
- CREATE PROCEDURE FROM file
This new SQL instruction allows to create a stored procude from a
source file.
* Enhanced SQL instructions :
- EXECUTE stmt [USING var-list] [INTO var-list]
The EXECUTE instruction now allows you to specify an INTO variable list.
- OPEN cursor [USING var-list] [WITH REOPTIMIZATION]
The OPEN cursor instruction now supports the reoptimization option.
* Connection handling
New connection handling instructions are provided (see Informix SQL reference
for more details about connection handling).
CONNECT TO [AS ] [USER USING ]
DISCONNECT
SET CONNECTION [DORMANT]
Warning: Multiple SQL sessions are not supported by INFORMIX when using the
shared memory protocol. A network protocol must be used instead.
* Unsupported SQL statements
ALLOCATE COLLECTION
DEALLOCATE COLLECTION
ALLOCATE ROW
DEALLOCATE ROW
ALLOCATE DESCRIPTOR
DEALLOCATE DESCRIPTOR
GET DESCRIPTOR
SET DESCRIPTOR
CHECK TABLE
REPAIR TABLE
INFO
OUTPUT
DESCRIBE
GET DIAGNOSTICS
* YEAR 2000 support
The DBCENTURY environment variable is now fully supported and a new attribute
("CENTURY") can be specified in form fields for user input.
The CENTURY attribute takes precedence over DBCENTURY whenever encountered.
The century indicator can be "P", "C", "F", "R" (not case sensitive).
Examples:
in a prompt instruction :
PROMPT "Enter the preferred start day for ", customer_name CLIPPED
ATTRIBUTE (YELLOW)
FOR req_date
ATTRIBUTE (BLUE,CENTURY="F")
in a form :
database stores
screen
{
Customer Name [c1 ]
Customer Address [c2 ]
Complaint_Date [c3 ]
}
tables
Customer
attributes
c1 = customer.name;
c2 = customer.address, wordwrap;
c3 = customer.date, format="ddmmyy", CENTURY="F";
* INPUT ARRAY extensions
The INPUT ARRAY instruction has been enhanced :
- The initial and max number of rows can be specified with the new "COUNT"
and "MAXCOUNT" attributes.
- The current row can now be automatically highlighted by using the
"CURRENT ROW DISPLAY" attribute.
- The insert and delete operations can be disabled with the "INSERT ROW"
and the "DELETE ROW" attribute.
- Insert and delete operations can be cancelled with the CANCEL INSERT and
CANCEL DELETE instructions, in BEFORE INSERT and BEFORE DELETE blocks.
- CANCEL INSERT must appear within the BEFORE INSERT clause
- CANCEL DELETE must appear within the BEFORE DELETE clause.
- CANCEL INSERT/DELETE terminates the BEFORE INSERT/DELETE clause like
NEXT FIELD does.
Input array example :
DEFINE n_rows INTEGER
DEFINE arrayname ARRAY[100] OF RECORD ...
INPUT ARRAY arrayname WITHOUT DEFAULTS FROM s_array.*
ATTRIBUTES(
COUNT = n_rows,
MAXCOUNT = n_rows,
INSERT ROW = FALSE,
DELETE ROW = TRUE,
CURRENT ROW DISPLAY = "REVERSE,BOLD"
)
BEFORE INSERT
CANCEL INSERT
BEFORE DELETE
LET n_rows = n_rows - 1
IF n_rows <= 0 THEN
CANCEL DELETE
END IF
END INPUT
* Application termination
For UNIX applications, the TERMINATE signal can now be trapped in order to
call a user function :
OPTIONS ON TERMINATE SIGNAL CALL
* Screen array size
It now possible to get the size (i.e., the declared dimension) of a named
screen array from 4GL programs. A new built-in function is provided
for this :
fgl_scr_size( {""|variable} )
* Hiding the comment line
To hide the comment line, a new attribute is supported in the OPEN WINDOW
instruction :
COMMENT LINE OFF
Example:
OPEN WINDOW w1 AT ... ATTRIBUTES( BORDER, COMMENT LINE OFF )
* The fglpager behavior has changed. When you reach the last page of a report
displayed to the screen, pressing the "next page" button ( or the "F6"
or "Escape" keys ) will no longer close the report viewer.
In such a case pressing the "next page" button will cause a message to appear
indicating that this is the last page of this report. To quit you have to
press the "Stop" button which will close the report but without sending an
interruption signal. For backward compatibility however, INT_FLAG variable
is set to true.
* The "fglrun.box.error" resource in the fglprofile configuration file is no
longer used when using the compiler/DVM on Microsoft Windows computers.
Errors are now always redirected to the standard output.
* Some error numbers have changed since version 2.10. Here is a complete list
of these changes. English messages texts can be found in following file :
"$FGLDIR/msg/en_us/0333/all.msg"
Removed error numbers:
-6106
-1500
-5010
-6021
-6320
Modified errors numbers:
-------------
Old New
-------------
-201 | -4333
-201 | -6801
-202 | -6611
-203 | -6612
-1600 | -6361
-1700 | -6360
-1900 | -6340
-1901 | -6321
-1902 | -6322
-1903 | -6323
-1904 | -6324
-1905 | -6325
-1906 | -6305
-1910 | -6327
-1400 | -6300
-1401 | -6301
-1402 | -6302
-1403 | -6303
-1404 | -6304
-1406 | -6306
-1407 | -6307
-1408 | -6308
-1409 | -6309
-1410 | -6310
-2000 | -6320
-2001 | -6341
-2002 | -6342
-2003 | -6343
-2004 | -6344
-2005 | -6345
-2006 | -6346
-5000 | -6200
-5001 | -6201
-5002 | -6202
-5003 | -6203
-5004 | -6204
-5005 | -6205
-5006 | -6206
-5007 | -6207
-5008 | -6208
-5100 | -6209
-5102 | -6210
-6004 | -6600
-6100 | -6601
-6101 | -6602
-6102 | -6362
-6103 | -6328
-6104 | -6329
-6105 | -6363
-6200 | -6603
-6300 | -6605
-6301 | -6606
-6400 | -6607
-6500 | -6608
-6800 | -6750
-6801 | -6751
-6802 | -6752
-6803 | -6753
-6804 | -6754
-6805 | -6755
-6806 | -6756
-6807 | -6757
-6808 | -6758
-6809 | -6759
-6810 | -6760
-7000 | -6601
* Note that if you want to use Global Language Support (GLS) with Four J's
Universal compiler 3.0, you need to use Informix Client SDK 2.x. To use
the GLS version of the compiler, run the fglmode utility on Unix with the
"-m GLS" parameters and create a P code runner with the fglmkrun script by
using the "-gls" flag.
To restore the ASCII version of the compiler, run fglmode with the option
"-m ASCII" and re-build a runner without the "-gls" flag.
* To create a GLS P code runner on NT, you will need to modify the makefile
located in the "%FGLDIR%\Example\Simple" directory: Set the "USE_GLS"
resource to "YES" and then run NMAKE , where can be one of :
RUNNER_NODB : runner without db interface
RUNNER_IX5 : runner with INFORMIX ESQL/C 5
RUNNER_IX71 : runner with INFORMIX ESQL/C 71
RUNNER_IX72 : runner with INFORMIX ESQL/C 72
RUNNER_IX9 : runner with INFORMIX ESQL/C 9x
RUNNER_IXGEN : runner with ESQLC db interface
Make sure you have the right environment settings for compilation ( FGL*
and Microsoft Visual C++ )
For more information read the header of the file %FLGDIR%\lib\winrunr.mk.
* Canvas has been enhanced. In previous versions, the canvas drawing area
was referenced by the tag name specified in the form specification file.
Now the field name is used to reference the canvas area. In order to keep
the same 4GL code, just modify the form specification files by using the
same name for the field and the field tag.
Example :
DATABASE FORMONLY
SCREEN {
[c01 ]
[c01 ]
[c01 ]
[c01 ]
[c01 ]
[c01 ]
}
ATTRIBUTES
c01 = formonly.mycanvas,widget="Canvas";
The field definition :
c01 = formonly.mycanvas,widget="Canvas";
Becomes:
c01 = formonly.c01,widget="Canvas";
This change was required because using the tag name can lead to problems in
certain complex situations.
Version 2.10.*
-------------------------------------------------------------------------------
* HTML Client
The HTML Client is an additional software component that enables Four J's
Universal 4GL applications to be displayed in a Web browser.
HTML can be embedded directly into 4GL forms and modules to further enhance
an application.
Use of this component is optional, and may require modification to existing
4GL code.
Information about the installation of the HTML Client software is available
in the Four J's Universal Compiler User Guide, Version 3.0. Documentation.
Explanation of the configuration and use of the HTML Client is available on
the product CD in HTML format.
* Client SDK support
This version of Four J's Universal 4GL compiler supports Informix Client
SDK 2.x (aka ESQL/C 9.1x).
The following command must be used to create a P code runner with the Client
SDK 2.xx database interface :
$ fglmkrun -sh esql -d ix914
$ fglmkrun -sh esql -d ix914 -add -static
The second line tries to create the runner using static libraries instead of
shared libraries. This may not work on all operating systems.
4.BUG CORRECTION LIST
===============================================================================
Version 2.10
-------------------------------------------------------------------------------
Note: The below bug numbers are taken from Four J's Development Tools.
11007
MENU MESSAGE NOT DISPLAYED WHERE EXPECTED
Description : Position the mouse cursor on the menu option "Third",
then press "F" on the keyboard. The first menu option
will be selected, and a subwindow will be displayed
for a few seconds. Do not touch the mouse. While the
first subwindow is still displayed, press "S" on the
keyboard. When the first window is removed and the
second is displayed, the menu prompt text that
should be displayed on the second line of the main
screen will instead be displayed on the second line
of the subwindow.
7292
ERROR LINE NOT ON CORRECT LINE
Description : After an OPTION ERROR LINE value that is different
from the default, if the OPTION statement is before
any I/O function (DISPLAY AT, ...), the error always
appears on the last line.
11008
CONSTRUCT ON A DATETIME YEAR TO SECOND DOES NOT GIVE A GOOD RESULT
Description : When you use a CONSTRUCT on a column declared as
DATETIME YEAR TO SECOND, the system adds the
BETWEEN keyword and divides the date in two parts
instead of creating an EQUAL query. It seems that the
separator ':' is responsible for the split.
11009
ERROR LINE DISPLAYED AT RANDOM ON THE SCREEN, DEPENDING ON MESSAGE
LINE
Description : The ERROR line is displayed differently on the
screen whether or not the message line is defined.
This occurs only in graphical mode.
11010
DISPLAY MESSAGE ON MESSAGE LINE IF ERROR LINE IS SET ON THE SAME LINE
Description : If you display a message on the ERROR line and then a
message on the MESSAGE line, and if the two lines are
defined on the same line, the message sent to the
MESSAGE line is not displayed.
7297
WITH TOOLBARS, THE ERROR LINE IS ALWAYS LAST -1
Description : With the toolbars enabled, the error line is
always LAST -1. For example, if you specify OPTION
ERROR LINE 3, the error still displays at Last -1.
11016
A DISPLAY OF YEAR() AFTER A 'USING' GIVES UNPREDICTABLE RESULTS
Description : With the instruction :
DISPLAY 6 USING '&&', YEAR(TODAY)
A space is inserted between the two characters taken
by the number 06 and the year given by YEAR.
Results are also incorrect if you use more or fewer
ampersands
5277
PROBLEM WITH DEFAULT CONCATENATION OF CHARACTER
Description : If a character string of length 10 and a
default assignation of 2 integers with 0 values was
specified, an incorrect string is generated.
5278
USING RECORD LIKE TABLENAME.* WITH MANY COLUMNS GIVES COREDUMP AT
COMPILE TIME
Description : In a 4GL program, if you use a variable with RECORD
LIKE tablename.* with a table that contains many
columns (more than 500), a "segmentation fault"
occurs at compile time.
12002
DECIMAL INSERTION.
Description : If a field is defined as DECIMAL(7,3) you can insert
8 digits without an error (no control of width).
INFORMIX-4GL 4.xx says "error in field" for the same
entry.
12002B
DECIMAL INPUT.
Description : If a field is defined as DECIMAL(7,3), and you input
more than 3 decimals, the value is rounded on the
screen, but retains all decimal places when you use
the value. INFORMIX-4GL rounds the value both in the
input and internally.
11005
EXTEND DOES NOT GIVE THE DAY AND THE MONTH
Description : With INFORMIX-4GL, EXTEND(v_date, DAY TO DAY) gives
the day of the DATE v_date and EXTEND(v_date, MONTH
TO MONTH) gives the month. Dynamic 4GL does not.
EXTEND(v_date, YEAR TO YEAR) works fine.
5279
COMPILER ERROR WITH DOS TEXT FILES.
Description : The compiler does not accept text files with a DOS
format (end of line \r\n) in .4gl and .per files.
5280
INFORMIX 7.22 ON NT SQLCA BAD RESULT
Description : On NT, with Informix ESQL/C 7.22, sqlca.sqlcode does not
return the correct value. This is because the sqlca
calls in ESQL/C are now functions instead of
structures.
5281
SECURITY HOLE : USER IDENTIFICATION ON NT
Description : On NT, implicit user names are used with the USERNAME
or LOGNAME variables. Internal Windows functions
should be used instead to specify user and login
names.
8102
CLICK IN A DISPLAY FIELD CAUSES A CORE DUMP ON SUN
Description : Under some conditions, a core dump (segmentation
fault) occurs on SUN systems.
6150
THE DBFORMAT VARIABLE DOES NOT WORK
Description : DBFORMAT does not work in ASCII or graphical mode.
In graphical mode you can use the key.translate
function to solve the problem, but in ASCII mode
the problem remains.
7254
UPSCOL ATTRIBUTE FOR DATES
Description : If you use the upscol tool to define a format for a
date field the attribute is not used at display. For
the field orders.ship_date, declaring the FORMAT like
"ddmmmyy" will not display the date because only 7
characters are available in the form.
10019
CONSOLE WITH SCO
Description : With SCO, a license problem message appears when
you attempt to run programs directly on the console
terminal. You must use another tty.
7255
INITIALIZE DATETIME TO NULL
Description : If a DATETIME field is not explicitly initialized to
NULL, inserting it in the database will produce
a record whose value is 0 (zero). With INFORMIX-4GL,
doing the same will produce a NULL record. With SINIX
server, it returns an error.
9060
UNLOAD A FLOAT DOESN'T UNLOAD THE RIGHT VALUE
Description : The UNLOAD function works differently from the same
function in INFORMIX-4GL. If you unload a field
defined as FLOAT that contains a NULL value,
0.0 is returned.
6507
FGLMKMSG WON'T COMPILE BIG HELP SECTIONS
Description : fglmkmsg won't compile a help file if a help section
of the file exceeds 32K.
5283
DISPLAY TO OF A FLOAT WITH NULL VALUE DISPLAYS 0.0
Description : If you invoke DISPLAY TO on a field defined as FLOAT
that contains a NULL value, the system displays the
value 0.0.
5284
SKIP LINES GIVES BAD RESULT IF IT SKIPS MORE LINES THAN A PAGE
Description : SKIP LINES gives a bad result if it skips more lines
than a page (page length, ...). INFORMIX-4GL
considers this statement as a "SKIP TO TOP OF PAGE".
11020
MULTIPLE INCLUDES OF A FIELD WITH VALIDATE LIKE
Description : Multiple INCLUDEs of a field with the VALIDATE LIKE
clause behave incorrectly.
6521
THE VERIFY STATEMENT IS IGNORED
Description : The VERIFY statement is ignored. The user should
be prompted twice for specifying a value in a field.
9069
THE NUMBER OF LINES WRITTEN ON ONE PAGE CHANGE MAY CHANGE
Description : After a SKIP xx LINES statement, the need for a new
page is not verified properly. The system returns
variable page lengths.
9071
A MOUSE DOUBLE CLICK DOES NOT RETURN THE CORRECT KEY BINDING
Description : If clicking on a button closes the current window
and the mouse pointer is then on another button,
this button is executed when the mouse is released.
12012
STATEMENT EVERY ROW GIVES COMPILE TIME ERRORS
Description : The EVERY ROW clause returns errors at compile time.
7303
REPORT WITHOUT OUTPUT DOESN'T DELETE THE TEMPORARY TABLE
Description : Repeating a REPORT with GROUP and without
OUTPUT returns a temporary table error
9081
PROMPT STATEMENT WITHOUT LABEL RESULTS IN ERROR -1146
Description : A prompt " " for char x works in a window with 1 row
and 1 column but results in an error with a window
with 2 rows and 1 column. The error may occur with
different window sizes.
9082
PRINT "" GENERATES A CORE DUMP
Description : The command PRINT "" in a report generates a
core dump. The command PRINT " " works fine.
9083
WRONG ARRAY INITIALIZATION
Description : The array rows which are initialized to NULL return
the value of the last not NULL row. The value NULL
or "" creates problems.
9084
THE SCROLL ATTRIBUTE DOES NOT FUNCTION PROPERLY
DESCRIPTION : The field option scroll does not work. The cursor
scrolls over the field.
Version 2.10.4c2
-------------------------------------------------------------------------------
5296
BAD UNLOAD FILE GIVES NO ERROR
DESCRIPTION : # Bad unload file gives no error
5304
LOAD WITH OWNER IN TABLE NAME DOESN'T RUN
DESCRIPTION : Gives -201 syntax error
5310
COMPILER ERROR: CANNOT USE SQLCA IN A DISPLAY STATEMENT
DESCRIPTION : The compiler generates an error: Cannot use
sqlca in a display statement.
6601
MENU OPTION WITH TRAILING SPACE CAUSES CORE DUMP
DESCRIPTION : Using a MENU option with a trailing space causes a
core dump on SUN. Forms statement error -1168. The
command '(null)' does not appear in the menu on
other systems when using SHOW/HIDE on this option
7023
GRANT SELECT SYNTAX CAUSES A COMPILER ERROR
DESCRIPTION : The GRANT SELECT syntax causes a compiler error.
7244
GRANT FOR
DESCRIPTION : The grant for a table is not accepted
7277
VARCHAR AFFECTED BY A SELECT LOSES THE LAST CHARACTER
DESCRIPTION : In SELECT INTO varchar, the last character is lost.
For example, instead of "1234567890", the varchar
receives "123456789"
7282
CLEAR A WORDWRAP, ONLY THE FIRST LINE IS CLEARED
DESCRIPTION : By using the command "clear fieldname" on a wordwrap
field, only the first line is cleared. With
INFORMIX-4GL, the entire wordwrap field is cleared.
7287
HIDE OPTION IN MENU IS NOT CHECKED
DESCRIPTION : On Sun systems, if there is a hide option in the menu
for a menu point that does not exist, a core dump
results.
7293
INFIELD DOES NOT GIVE AN APPROPRIATE VALUE WHEN PRESSING RETURN ONLY
DESCRIPTION : If there is a question with INFIELD in the
"after input", an improper value is returned if you
change fields with the return key. If you press the
accept key, the normal behavior is exhibited.
7314
PRINTING A TEXT VARIABLE RESULTS IN EMPTY REPORT
DESCRIPTION : Using a variable declared as text in a report results
in an empty report.
7324
DATE: CONVERSION ERROR IN INPUT
DESCRIPTION : Concerning DBDATE=Y4DM-, Dynamic 4GL does not permit
formats such as "981010". A conversion error results.
With INFORMIX-4GL version 6.xx, it is possible.
With INFORMIX-4GL version 4.xx, it is not possible.
7329
DISPLAY "" AT X,Y WITH THE ASCII CLIENT MAY CRASH
DESCRIPTION : Doing a "DISPLAY "" AT X,Y" with X,Y specifying a
location outside of the screen crashes the
application.
With Sun solaris it core dumps. With Linux you
may have the "Virtual memory exceeded in 'new'" error
message before the core dump.
8079
INTERNAL ERROR WITH INPUT ARRAY USED AS DISPLAY ARRAY WITH EXIT AT
BEFORE ROW
DESCRIPTION : When using a BEFORE ROW EXIT INPUT in an input array,
a core dump results.
8094
SPACES DOES NOT CREATE SPACE
DESCRIPTION : If you init a string with SPACES, tests on this
string do not indicate any space but instead show a
NULL. INFORMIX-4GL creates real SPACES.
9075
STRING CONVERSION ERROR ON SETTING A DATE WHEN DBDATE IS SET TO DMY2/
DESCRIPTION : With DBDATE set to DMY2/, the instruction
"let a_date = '01/01/1956'" results in an
error : -1218 String to date conversion error.
INFORMIX-4GL does not produce this error. The same
problem occurs with the LOAD command.
9079
VERIFY & PICTURE IN UPSCOL DO NOT FUNCTION PROPERLY
DESCRIPTION : When you define a picture or property on a
field in a table with UPSCOL, it does not work.
9080
4GL COMMAND GRANT INDEX IS NOT ALLOWED WITH DYNAMIC 4GL
DESCRIPTION : In Dynamic 4GL, INDEX is not recognized as a table
privilege.
11011
VIEWS CANNOT HAVE OWNER NAMES SPECIFIED
DESCRIPTION : When you create a view with the owner name specified,
the program does not compile (grammatical error).
With INFORMIX-4GL, it functions properly.
11019
THE LOAD OF A TEXT TYPE DOES NOT WORK
DESCRIPTION : When you execute a LOAD of a TEXT column, an SQL
statement error occurs : -608 Illegal attempt to
convert Text/Byte blob type.
4021
CHANGING FONT ON A RUNNING APPLICATION CAN MAKE A RUNNER GPF ON NT
DESCRIPTION : This bug appears with a specific 4GL code instruction
set. When you change the font, you may have a GPF
( General Protection Fault ). To resolve temporary
this bug in the file "fgl2c.tcl", you should replace
the last line of the procedure named "fglChooseFont":
fglRedraw $dpyChannel 0
by :
# fglRedraw $dpyChannel 0
(only if you have an older version in which this
changes have not been corrected)
This bug only occurs with the second version of the
fgl2c.tcl file.
NOTE: To change the font displayed in a running
application, you will need to perform the following
steps:
1) Select "Fonts" from the magic lamp icon in the
upper left corner of your application window, and
select the desired font.
2) Select "Save Config" from the magic lamp icon.
3) Exit the application.
4) Click the "Reload" button of the 4GL-Server.
5) Relaunch your application.
Version 2.13
-------------------------------------------------------------------------------
9075
STRING CONVERSION ERROR ON SETTING A DATE WHEN DBDATE IS SET TO DMY2/
Description ..... With dbdate set to DMY2/, the instruction let a_date
= '01/01/1956' gives an error -1218 String to date
conversion error. It works with I4GL. The same
problem occurs with the LOAD command.
5296
BAD UNLOAD FILE GIVES NO ERROR
Description ..... bad unload file gives no error
5304
LOAD WITH OWNER IN TABLE NAME DOESN'T RUN
Description ..... LOAD WITH OWNER IN TABLE NAME DOESN'T RUN. Gives -201
syntax error
5302
GLS: LOAD STATEMENT WITH MULTI-BYTE TABLENAME IS NOT ACCEPTED
Description ..... LOAD STATEMENT WITH MULTI-BYTE TABLENAME IS NOT
ACCEPTED.
5294
PROBLEM WITH REPORT "EVERY ROW" SYNTAX
Description ..... # give next error of compilation:
b5294.4gl:18: Fatal INTERNAL error: c_report.c(255).
in version 2.10: Default report generated with "EVERY ROW"
statement is not implemented yet. print a clipped#| A
grammatical error has been found at "print" expecting: END.
in Informix version: print a clipped
A grammatical error has been found on line 30, character 12.
First seen in ... 2.13.004
5305
GLS: MULTI-BYTE TABLENAME CONTAINS '^' CANNOT BE FOUND BE THE COMPILER
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... cannot compile because the name of the table contains
multi-byte with '^'
First seen in ... 2.13.005
5300
GLS: DEFAULT MONEY PRECISION SCALE IS NOT USED
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
dbmoney="\\"
Description ..... DEFAULT MONEY PRECISION SCALE IS NOT USED.
so 123 is display \123.00 and not \123
1234567890123456 is not accepted, Informix accepts it
First seen in ... 2.13.005
5303
GLS: IN REPORT DIFFERENCE WITH WORDWRAP AND MULTI-BYTE
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... Difference in word-wrap of report with multi-byte
character.
First seen in ... 2.13.005
5306A
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMGY2/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMGY2/
First seen in ... 2.13.005
5306B
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMEY2/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMEY2/
First seen in ... 2.13.005
5306C
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMGY4-
First seen in ... 2.13.005
5306D
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMEY4-
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DMEY4-
First seen in ... 2.13.005
5306E
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MGY2D/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MGY2D/
First seen in ... 2.13.005
5306F
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MEY2D/
System .......... Informix with GLS 3.07
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MEY2D/
First seen in ... 2.13.005
5306G
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MGY4D/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
program links with b5306fct.4gl
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MGY4D/
First seen in ... 2.13.005
5306H
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MEY4D/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
program links with b5306fct.4gl
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=MEY4D/
First seen in ... 2.13.005
5306I
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DGY4M/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
program links with b5306fct.4gl
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DGY4M/
First seen in ... 2.13.005
5306J
GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DEY4M/
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/DATETIME WITH DBDATE=DEY4M/
First seen in ... 2.13.005
5307A
GLS: BAD RESULT OF DATE/MONEY WITH DBDATE=MDGY4/ AND DBMONEY=\\
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/MONEY WITH DBDATE=MDGY4/ AND
DBMONEY=\\
First seen in ... 2.13.005
5307B
GLS: BAD RESULT OF DATE/MONEY WITH DBDATE=MDEY4/ AND DBMONEY=\\
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/MONEY WITH DBDATE=MDEY4/ AND
DBMONEY=\\
First seen in ... 2.13.005
5307C
GLS: BAD RESULT OF DATE/MONEY WITH DBDATE=MDY4/ AND DBMONEY=\\
System .......... Informix with GLS 3.07
client_locale=ja_jp.sjis
Description ..... GLS: BAD RESULT OF DATE/MONEY WITH DBDATE=MDY4/ AND
DBMONEY=\\
First seen in ... 2.13.005
Version 2.13.016
-------------------------------------------------------------------------------
Bug # : 5311 Appeared the : 13/11/1998 in version : 2.10.2a1
Description : LOAD WITH OWNER IN TABLE NAME DOESN'T RUN WITH ANSI MODE
LOAD WITH OWNER IN TABLE NAME DOESN'T RUN with ANSI Mode. Gives
-205 syntax error
Bug # : 5294 Appeared the : 29/10/1998 in version : 2.13.004
Description : PROBLEM WITH REPORT "EVERY ROW" SYNTAX
# give next error of compilation: b5294.4gl:18: Fatal INTERNAL
error: c_report.c(255). in my version 2.10: Default report
generated with "EVERY ROW" statement is not implemented yet. print
a clipped#| A grammatical error has been found at "print"
expecting: END. in Informix version: print a clipped A grammatical
error has been found on line 30, character 12
Bug # : 5296 Appeared the : 29/10/1998 in version : 2.10.2a1
Description : BAD UNLOAD FILE GIVES NO ERROR
# bad unload file gives no error
Bug # : 5302 Appeared the : 03/11/1998 in version : 2.13.005
Description : GLS: LOAD STATEMENT WITH MULTI-BYTE TABLENAME IS NOT ACCEPTED
LOAD STATEMENT WITH MULTI-BYTE TABLENAME IS NOT ACCEPTED.
Bug # : 5305 Appeared the : 03/11/1998 in version : 2.13.005
Description : GLS: MULTI-BYTE TABLENAME CONTAINS '^' CANNOT BE FOUND BE THE
COMPILER
cannot compile because the name of the table contains multi-byte
with '^'
Bug # : 5325 Appeared the : 07/12/1998 in version : 2.02.3b2
Description : LAST CHARACTER IN A VARCHAR IS NOT LOAD/UNLOADED
LAST CHARACTER IN A VARCHAR IS NOT LOAD/UNLOADED
Bug # : 5312 Appeared the : 13/11/1998 in version : 2.10.3a3
Description : NESTED UNION WITH PARENTHESIS AREN'T SUPPORT AT COMPILE
NESTED UNION WITH PARENTHESIS AREN'T SUPPORT AT COMPILE
Bug # : 5313 Appeared the : 13/11/1998 in version : 2.13.008
Description : ^L NOT SUPPORTED IN 4GL SOURCE CODE
^L NOT SUPPORTED IN 4GL SOURCE CODE
Bug # : 5314 Appeared the : 13/11/1998
Description : '\0' ARE INTERPRETED LIKE '0', INFORMIX LIKE 'ASCII 0'
'\0' ARE INTERPRETED LIKE '0', INFORMIX LIKE 'ASCII 0'
Bug # : 5317 Appeared the : 13/11/1998 in version : 2.13.008
Description : BAD REPORT WITH PAGE TRAILER THAT FINISHES BY ";"
BAD REPORT WITH PAGE TRAILER THAT FINISHES BY ";"
Bug # : 5329 Appeared the : 11/12/1998 in version : 2.13.007
Description : GLS: FORM COMPILATION ERROR WITH A CHARACTER > 127 AND A DELIMITER
WITHOUT SPACE
The error is in the "fglform" compiler. Using the character from
the national character set (>127) in front of delimiter makes the
compiler confused. He isn't able to find the field. Leaving a
space or another ASCII character between accented character and
field delimiter doesn't cause this error. The environment in this
case was set:
LANG=cs_CZ.iso88592;DB_LOCALE=cs_cz.8859-2;CLIENT_LOCALE=cs_cz.885
9-2
Bug # : 7314 Appeared the : 04/09/1998 in version : 2.02.1e6l6
Description : PRINTING A TEXT VARIABLE GIVES EMPTY REPORT
using a variable declared as text in a report results in an empty
report.
Bug # : 5297 Appeared the : 29/10/1998 in version : 2.02.3b1
Description : CANNOT COMPILE A SPECIAL DISPLAY EXPRESSION
#cannot compile this expression MAIN display "sqlca.sqlerrd[3] =
",sqlca.sqlerrd[3] using "<<<<&"
Bug # : 5316 Appeared the : 13/11/1998 in version : 2.13.008
Description : DBCENTURY=F AND DATETIME GIVES BAD RESULT
DBCENTURY=F AND DATETIME GIVES BAD RESULT. Not verify other value
of DBCENTURY
Bug # : 5297 Appeared the : 29/10/1998 in version : 2.02.3b1
Description : CANNOT COMPILE A SPECIAL DISPLAY EXPRESSION
#cannot compile this expression MAIN display "sqlca.sqlerrd[3] =
",sqlca.sqlerrd[3] using "<<<<&"
Bug # : 5304 Appeared the : 03/11/1998 in version : 2.10.2a1
Description : LOAD WITH OWNER IN TABLE NAME DOESN'T RUN
LOAD WITH OWNER IN TABLE NAME DOESN'T RUN. Gives -201 syntax error
Bug # : 5305 Appeared the : 03/11/1998 in version : 2.13.005
Description : GLS: MULTI-BYTE TABLENAME CONTAINS '^' CANNOT BE FOUND BE THE
COMPILER
cannot compile because the name of the table contains multi-byte
with '^' run "sh b5305.sh" (gives error -4320)
Bug # : 5310 Appeared the : 13/11/1998 in version : 2.02.3b2
Description : COMPILER ERROR: CANNOT USE SQLCA IN A DISPLAY WITH USING OR
CLIPPED
COMPILER ERROR: CANNOT USE SQLCA IN A DISPLAY STATEMENT
Version 3.00
-------------------------------------------------------------------------------
Bug # : 4018A
Description : CANVAS DOES NOT RUN CORRECTLY WITH WTK 1.47 AND COMPILER
VERSION 2.13.023
Full description : When you run canvas using windows front-end version 1.47
and the compiler version 2.13.023, no canvas object is
drawn in the canvas area.
Appeared the : 08/04/1999
Apparition version : 1.47
Correction version : 2.91.008
Bug # : 4020
Description : PASSING A NON DECLARED RECORD TO A FUNCTION MAKES A GPF ON
NT
Full description : If you call a function with a record as parameter you get a
GPF during the compilation only if the record is defined in
the calling function. On Unix you get two errors : One for
the variable which is not defined when the function is
called One in the function, because the function has
already been called with a different number of parameters
Appeared the : 14/01/1999
Apparition version : 2.10.4c2
Correction version : 2.91.013
Bug # : 4020B
Description : PASSING A NON DECLARED RECORD TO A FUNCTION MAKES A
COREDUMP
Full description : If you call a function with a record as parameter you get a
coredump.
Appeared the : 10/05/1999
Apparition version : 2.13.023
Correction version : 2.91.013
Bug # : 5284B
Description : SKIP LINES GIVES BAD RESULT IF IT'S TO BIG FOR A PAGE
Full description : Skip lines gives bad result if it's too big for a page
(page length, ...). Informix-4gl considers this statement
like a SKIP TO TOP OF PAGE
Appeared the : 24/03/1999
Apparition version : 2.10.4c2
Correction version : 2.91.010
Bug # : 5285
Description : BAD REINITIALIZATION OF REPORT
Full description : 4js: bad reinitialization of report (bad first Page
header) ix : An extra page header will show up on the
second page of the second report run if a skip to top of
page was the last command executed in the on every row
section of the previous report.
Appeared the : 29/10/1998
Apparition version : 2.02.3b1
Correction version : 2.91.010
Bug # : 5300A
Description : GLS: DEFAULT MONEY PRECISION SCALE IS NOT USED
Full description : DEFAULT MONEY PRECISION SCALE IS NOT USED. Ex: 123 is
display \123.00 and not \123 1234567890123456 is not
accepted, Informix accepts it
Appeared the : 07/04/1999
Apparition version : 2.13.023
Correction version : 2.91.010
Bug # : 5318
Description : IN CREATE TABLE, BLOB "IN" SYNTAX NOT ACCEPTED
Full description : IN CREATE TABLE, BLOB "IN" SYNTAX NOT ACCEPTED. ex: create
table b (b text in table)
Appeared the : 02/12/1998
Apparition version : 2.02.3b1
Correction version : 2.91.012
Bug # : 5320A
Description : LENGTH OF VARIABLE OF A TYPE TEXT GIVES 0
Full description : LENGTH OF VARIABLE OF A TYPE TEXT GIVES 0
Appeared the : 02/12/1998
Apparition version : 2.10.4c1
Correction version : 2.91.012
Bug # : 5320B
Description : IF A TEXT IS NULL, THE DISPLAY IN A FIELD IS NOT UPDATED
Full description : IF A TEXT IS NULL, THE DISPLAY IN A FIELD IS NOT UPDATED
Appeared the : 02/12/1998
Apparition version : 2.10.4c1
Correction version : 2.91.012
Bug # : 5320C
Description : TEXT FIELD DEFAULT PROGRAM IS DBEDIT
Full description : With TEXT Field in a form, default program is DBEDIT. d4gl
says No PROGRAM= clause for this field.
Appeared the : 02/12/1998
Apparition version : 2.10.4c1
Correction version : 2.91.012
Bug # : 5322
Description : BLOB PASSED IN PARAMETER OF FUNCTION IS NOT WELL
INITIALIZED (ERR -452)
Full description : BLOB PASSED IN PARAMETER OF FUNCTION IS NOT WELL
INITIALIZED. Gives error -452
Appeared the : 02/12/1998
Correction version : 2.91.010
Bug # : 5359
Description : IN GUI, ONLY LABEL BUTTON KEY BELOW F25 ARE DISPLAYED AS
LABEL
Full description : IN GUI, ONLY LABEL BUTTON KEY BELOW F25 ARE DISPLAYED.
Appeared the : 17/02/1999
Apparition version : 2.10.4c2
Correction version : 2.91.010
Bug # : 5364
Description : CHARACTERS '\' ARE NOT WELL TRANSMITTED TO THE DATABASE
ENGINE
Full description : CHARACTERS '\' ARE NOT WELL TRANSMITTED TO THE DATABASE
ENGINE.
Appeared the : 19/04/1999
Apparition version : 2.91.002
Correction version : 2.91.013
Bug # : 5365
Description : UNABLE TO USE THE NEXT FIELD OPTION IN A CONSTRUCT
STATEMENT
Full description : It is impossible to compile a program having a "next field"
option in a construct statement : you get the error message
: -4463 "The NEXT FIELD STATEMENT can only be used within
an INPUT or CONSTRUCT STATEMENT."
Appeared the : 03/05/1999
Apparition version : 2.91.007
Correction version : 2.91.010
Bug # : 5366
Description : LOAD STATEMENT HAS A BAD INTERPRETATION OF BACKSLASH AT END
OF LINE
Full description : LOAD STATEMENT HAS A BAD INTERPRETATION OF BACKSLASH AT END
OF LINE
Appeared the : 03/05/1999
Apparition version : 2.91.009
Correction version : 2.91.010
Bug # : 5367
Description : ONE EMPTY BLANK LINE AFTER EVERY MESSAGE ERROR
Full description : ONE EMPTY BLANK LINE AFTER EVERY MESSAGE ERROR.
Appeared the : 17/05/1999
Apparition version : 2.91.012
Correction version : 2.91.013
Bug # : 5368
Description : PROGRAM NAME IS WITHOUT EXTENSION WHEN A ERROR OCCURS
Full description : PROGRAM NAME IS WITHOUT EXTENSION WHEN A ERROR OCCURS:
Program stopped at "b5368", line number 2. SQL statement
error number -253. Identifier too long - maximum length is
18.
Appeared the : 17/05/1999
Apparition version : 2.91.012
Correction version : 2.91.013
Bug # : 6602
Description : DOC WATSON ON UNDEFINED PARAMETER
Full description : Not defining the parameter of a function causes a Doc
Watson on NT whereas on Unix it generates a very honest
.err file
Appeared the : 30/11/1998
Apparition version : 2.02.1e6l9
Correction version : 2.91.010
Bug # : 7218
Description : A 4GL FUNCTION ONLY CALLED FROM A C PROGRAM IS NOT KNOWN AT
RUNTIME
Full description : If a 4GL function, located in a module which contains only
4GL functions which are called by C functions, is called,
the program stops with an error function not defined.
Appeared the : 18/04/1998
Apparition version : 2.02.1e4
Correction version : 2.91.013
Bug # : 7272
Description : TOO BIG VALUE IN DECIMAL IS NOT CONTROLLED
Full description : Giving a value too big to a decimal gives no error With
Informix, an error appears : Decimal or money value exceeds
maximum precision.
Appeared the : 25/03/1998
Apparition version : 2.02.1e6k3
Correction version : 2.91.010
Bug # : 7275
Description : CALCULATION GIVES A RESULT INSTEAD OF ERROR
Full description : By a simple calculation, 4Js gives a result but Informix
gives an error because of the lack of precision place. This
can give big calculation error.
Appeared the : 22/04/1998
Apparition version : 2.02.1e6k3
Correction version : 2.91.010
Bug # : 7327
Description : SUM() WHERE IN REPORT GIVES NOT THE GOOD RESULT
Full description : In report, with print sum() where ... doesn't give the good
result. the part where is ignored
Appeared the : 17/11/1998
Apparition version : 2.02.3b1
Correction version : 2.91.012
Bug # : 7332
Description : CHANNEL::READ CRASHES IF FILE DOESN'T EXIST
Full description : If in a program, the function channel::read tries to read a
file that doesn't exist, the program crashes with the
following error : A function has not returned the correct
number of values expected. The same if you have WHENEVER
ERROR CONTINUE
Appeared the : 23/11/1998
Apparition version : 2.02.3b1
Correction version : 2.91.013
Bug # : 7337
Description : ERROR LINE NOT DISPLAYED WHEN WINDOW IS SMALLER THAN
DEFAULT
Full description : In graphical mode only, when the screen has a smaller
height than the default value ( 25 ) with options error in
last line, no error is displayed.
Appeared the : 28/01/1999
Apparition version : 2.02.3b1
Correction version : 2.91.008
Bug # : 7343
Description : VALIDATE GIVES ERROR -1321
Full description : Statement VALIDATE gives error -1321 at runtime even if
variables have good values. Classic Informix 4GL gives no
error.
Appeared the : 12/02/1999
Apparition version : 2.02.3b1
Correction version : 2.91.012
Bug # : 8109
Description : FGL2P -O CRASHES ON SUN WITH NON DECLARED FUNCTION ARGUMENT
Full description : When you define a function with an argument, but you do not
declare this argument, on a SCO system you get error #4336.
On Sun Solaris 2.5 and 2.6 you get a core dump.
Appeared the : 09/07/1998
Apparition version : 2.02.1e6l9
Correction version : 2.91.010
Bug # : 9012
Description : WHEN THERE ARE TOO MUCH STATEMENT IN A ON KEY, FGL2P
DOESN'T COMPILE
Full description : With too much keys defined in a ON KEY statement fgl2p and
fgl2c don't compile the code. There is no warn, it just
doesn't compile.
Appeared the : 11/06/1998
Apparition version : 2.02.1e4c
Correction version : 2.91.013
Bug # : 9050
Description : ON NT WINDOW CANNOT BE CLOSED LIKE MICROSOFT WINDOWS
Full description : The window cannot be closed like a Microsoft windows. Can
we have some entry in the fglprofile which define a
function key to send or better a function to run when this
button is pressed.
Appeared the : 18/03/1998
Apparition version : 2.02.1e6k3
Correction version : 2.91.010
Bug # : 9082B
Description : PRINT HEADER WITHOUT "ON EVERY ROW" GENERATES AN EMPTY
REPORT
Full description : In report, if you use the instruction "PAGE HEADER" without
using the instruction "ON EVERY ROW", the report is empty.
Appeared the : 24/02/1999
Apparition version : 2.13.019
Correction version : 2.91.010
Bug # : 9098
Description : UNDEFINED ARGUMENT IN A FUNCTION DESCRIPTION DUMPS CORE
Full description : An undefined argument in a function description at compile
time dumps core
Appeared the : 14/01/1999
Apparition version : 2.10.4c2
Correction version : 2.91.010
Bug # : 9109
Description : TEXT VARIABLES CAN'T BE PASSED AS PARAMETER
Full description : Text variables are not passed as parameter
Appeared the : 23/02/1999
Correction version : 2.91.010
Bug # : 9115B
Description : THE F4GL LOAD COMMAND DOESN'T USE THE SAME SQL WAY AS I4GL
Full description : The Four J's Load command doesn't use the same SQL command
as the I4GL Load command. The Four J's Load command doesn't
use an insert cursor.
Appeared the : 25/03/1999
Apparition version : 2.10.4c2
Correction version : 2.91.010
Bug # : 11021
Description : AN INPUT ON A TEXT FIELD USING AN EDITOR DOES NOT HANDLE
LINE FEEDS
Full description : When using an editor to enter data into a TEXT field (via
an INCLUDE, by typing ! in the field), the line feeds are
replaced by ?. Not with INFORMIX.
Appeared the : 16/07/1998
Correction version : 2.91.012
Bug # : 11030
Description : IN .PER FILES TABLE FORMONLY ARE NOT ACCEPTED
Full description : In a .per file, in the table section : table "formonly"
statement is not accepted.
Appeared the : 23/04/1999
Apparition version : 2.91.006
Correction version : 2.91.010
Bug # : 12024
Description : FGLWRT GIVES SYSTEMATICALLY AN ERROR BECAUSE OF POPEN
Full description : If a customer has problems with his licence (error message
like 6042) and finally you receive the message :
75575928527234387937932 No Error - Invalid Serial Number,
this is a problem with the instruction popen. It is
directly used by fglwrt to check the licence and is part of
the mscvrt.dll. This problem is directly linked to the
version of the system you install, or more precisely the
version of Microsoft Internet Explorer (4.0 causes the
problem) or outlook express.
Appeared the : 05/02/1999
Correction version : 2.91.013
Bug # : 12027
Description : A DISPLAY AT FIRST LINE DOESN'T WORK WHEN THE MENU IS
DEFINED AT AN OTHER LINE
Full description : ONLY IN ASCII MODE : If a program define the menu line to
an other line than 1. A display at the first line of the
screen doesn't work.
Appeared the : 22/02/1999
Apparition version : 2.10.4c2
Correction version : 2.91.012
Bug # : 12033
Description : FGL_KEYSETLABEL AND MENUS WHICH CALL EACH OTHER
Full description : fgl_keysetlabel is implemented and documented as a global
setting function. This means that if fgl_keysetlabel() is
called in the main block for example, and a second time in
a function, when returning to the main block, the key label
is the one set in the function. In this release,
fgl_keysetlabel() is only available locally in a module,
whereas it is not in latest versions.
Appeared the : 11/03/1999
Apparition version : 2.10.4c2
Correction version : 2.91.010
Bug # : 12039
Description : THE INSTALLATION PROCEDURE FAILS WHEN /TMP IS FULL
Full description : By default, the installation script uses the /tmp directory
to extract files. If there is not enough space in that
directory, the installation fails with the message : "not a
gzip file"
Appeared the : 20/04/1999
Apparition version : 2.10.4c2
Correction version : 2.91.012
Bug # : 13001
Description : INPUT ARRAY MAXCOUNT ATTRIBUTE NOT SET TO COUNT WHEN IT IS
LESS THAN COUNT
Full description : The 'MAXCOUNT' attribute should default to the value of
'COUNT' when MAXCOUNT is less than 'COUNT'. For example, in
input array ... attributes( count=10, maxcount=1 ) maxcount
should default to 10.
Appeared the : 26/04/1999
Apparition version : 2.91.007
Correction version : 2.91.012
Bug # : 13002
Description : STRING CONSTANT WITH BACKSLASH NEW LINE
Full description : When using a backslash followed by a new line in a 4GL
string constant, a unexpected blank character appears in
the result string.
Appeared the : 26/04/1999
Apparition version : 2.91.007
Correction version : 2.91.012
Bug # : 13003
Description : COMPILER CRASHES WHEN EXPRESSION USES A HUGE NUMBER OF
DOUBLE PIPE OPERATORS
Full description : The compiler crashes when an expression uses a huge number
of double pipe concatenation operators
Appeared the : 26/04/1999
Apparition version : 2.91.007
Correction version : 2.91.012
Bug # : 16007
Description : LOAD FROM "" DOES NOT WORK WHEN USING A FILE LOGGED
DATABASE (WITH SE)
Full description : When creating a SE database with a log file, the statement
LOAD FROM "" INTO gives an error.
Appeared the : 12/05/1999
Apparition version : 2.91.007
Correction version : 2.91.012
Bug # : 11029
Description : DBDATE DMY40 DOES NOT WORK
Full description : When you set DBDATE to DMY40 it uses "0" as a delimiter
whereas there should be no delimiter.
Appeared the : 19/04/1999
Apparition version : 2.02.1e6l6
Correction version : 2.10.4c7
Bug # : 12030A
Description : FOREACH DOESN'T SET STATUS WHEN USING A "SELECT FOR UPDATE"
CURSOR
Full description : When using a cursor declared with a SELECT FOR UPDATE to
lock rows and a WHENEVER ERROR CONTINUE, FOREACH
instruction does not set STATUS to -250 when the required
row is already locked by another process. Standard I4GL
FOREACH sets STATUS when the row is locked by another
process.
Appeared the : 08/03/1999
Apparition version : 2.10.4c2
Correction version : 2.10.4c5
Bug # : 12036
Description : ROWID KEYWORD IN A SQL COMMAND MAKES THE FGLRUN CRASH
Full description : With a version 2.10.4c2 using database interface ESQL 9.14,
a DECLARE with a SELECT ROWID,... makes the program crash.
The same SELECT in an ESQL/C program works.
Appeared the : 29/03/1999
Apparition version : 2.10.4c2
Correction version : 2.10.4c5
Bug # : 7354
Description : TYPE BLOB ( LOC_T ) NOT DECLARED IN COMPILER
Full description : to use poplocator, the structure loc_t for declaration of
blob or text is not defined in the compiler
Appeared the : 23/04/1999
Apparition version : 2.91.005
Bug # : 9046
Description : ADD A JUSTIFY POSSIBILITY FOR THE BUTTON LABEL
Full description : The button label is always centered, there should be a way
to justify (left, right, centered) it.
Appeared the : 16/03/1998
Apparition version : 2.02.1e6k3
Correction version : 3.00.1e
Bug # : 11023
Description : POSITION OF THE FIRST WINDOW OF AN APPLICATION CHANGES
Full description : When you start and close an application with FGLRUN several
times, the first window has different positions slightly
descending at each time. The window should always be at the
same position if there is only one application running.
Appeared the : 15/02/1999
Apparition version : 2.10.4c2
Correction version : 3.00.1e
Bug # : 16006
Description : BMP CANNOT BE DISPLAYED IN CONTROL FRAME
Full description : a bmp picture cannot be displayed in the control frame
area.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Correction version : 3.00.1e
Bug # : 5348
Description : STATEMENT DISPLAY FORM DOESN'T CLEAR THE PREVIOUS FORM IN
THE GRAPHIC MODE.
Full description : Statement DISPLAY FORM doesn't clear the previous form in
the graphic mode. Informix-4gl makes close first the oldest
form before it displayed the form in the current window.
Doesn't appear in 2.11.xx
Appeared the : 22/01/1999
Correction version : tcl 3.16.2d3
Bug # : 7318
Description : TCL3: PB OF REFRESH
Full description : In the input array, if you select a word for cut/paste and
move the cursor with the arrow keys, there is a problem
with the refresh. run : b7318.sh ( set the profile file and
compile and run it )
Appeared the : 21/09/1998
Apparition version : 2.02.3a1
Correction version : tcl 3.16.2d
Bug # : 7328
Description : WITHOUT OOB, NOT POSSIBLE TO INTERRUPT WITH KEY WHEN
TRANSLATED
Full description : With gui.useOOB.interrupt = 0, it is not possible to
interrupt with interrupt key if it is translated to
another. The only possibility to interrupt is to use the
mouse click. run b7328.sh
Appeared the : 17/11/1998
Apparition version : 2.02.3b1
Correction version : tcl 3.16.2e
Bug # : 7339
Description : TCL3: GIVING A VALUE ON LAST POSITION APPEARS ON FIRST
BECAUSE OF AUTONEXT
Full description : In a field with a default value having the attribute
"autonext", if you overwrite the last character of the
field, the value appears on the first position because of
the attribute autonext ( only one field in the input )
Appeared the : 09/02/1999
Apparition version : 2.02.3b1
Correction version : tcl 3.16.3f
Bug # : 7347
Description : TCL3: COMBO BOX DOESN'T WORK
Full description : In tcl3, the combo box doesn't work.
Appeared the : 08/03/1999
Apparition version : 2.10.4c2
Correction version : tcl 3.16.4i
Bug # : 9090
Description : TCL3 INPUT ARRAY AFTER INSERTING A NEW LINE VALUES ENTERED
AREN'T DISPLAYED
Full description : In TCL3, after inserting a new row, values entered are not
displayed in the right field but in the last known row.
Appeared the : 09/12/1998
Apparition version : 2.02.3b1
Correction version : tcl 3.16.2d
Bug # : 11001
Description : PROBLEMS WHEN USING A COMBO BOX
Full description : The shortcut of a combo box is activated even when the
combo is not included in an INPUT
Appeared the : 21/04/1998
Apparition version : 2.02.1e615
Correction version : tcl 3.16.2d
Bug # : 12022
Description : DUMMY LINES WHEN VALIDATING A DISPLAY ARRAY
Full description : see in the example : validate a line and see the wrong
blank lines that appears. with wtk the problem only appears
with tcl3 (run FGLPROFILE=b12022.prof, it's frozen..) with
X11 : appears in TCL2 and TCL3
Appeared the : 25/01/1999
Apparition version : 2.02.1e6l6
Correction version : tcl 3.16.2b
Bug # : 5361
Description : NO SELECTION (CUT&PASTE) OF LAST CHARACTER OF A ENTRY WITH
TKORGENTRYS==0
Full description : YOU CANNOT SELECT THE LAST CHARACTER OF A ENTRY WITH
TKORGENTRYS==0
Appeared the : 24/02/1999
Apparition version : wtk 1.47
Correction version : wtk 1.482
Bug # : 6509
Description : CLEAR SCREEN AFTER A DIALOG DOES NOT WORK
Full description : After a dialog the clear form or screen doesn't work. Try
the example with the wtk1.44
Appeared the : 04/06/1998
Apparition version : 1.44
Correction version : wtk-1.448
Bug # : 5274B
Description : PROBLEM WITH PAGE TRAILER AND SEMI-COLON WITH
DBPRINT=FGLSERVER
Full description : if the PAGE TRAILER finishes with an instruction like PRINT
"blabla"; and you have DBPRINT=FGLSERVER or you print to
the screen, you don't get "Page Trailer" at the end of the
page.
Workaround : Work around: use TOP OF PAGE instruction in OUTPUT FORMAT
Appeared the : 29/04/1999
Apparition version : 2.91.008
Bug # : 5341B
Description : GLS: IN REPORT, START REPORT TO FILE IS NOT
SUPPORTED
Full description : The syntax "start report to file" where file is
a variable is not supported because file is now a keyword.
Workaround : Rename your variable file with another name (example :
filename) or replace your line by "start report
to file file".
Appeared the : 04/05/1999
Apparition version : 2.91.006
Bug # : 10033A
Description : THE GUI.TOOLBAR.X.KEY RESOURCE SHOULD BE CASE INSENSITIVE
Full description : The gui.toolBar.X.key resource should be case insensitive
Appeared the : 11/05/1999
Apparition version : 2.91.007
Bug # : 10033B
Description : THE KEY RETURNED BY CANVAS, BMP, BUTTONS, RADIO/CHECKS IS
CASE SENSISTIVE
Full description : The key returned by the canvas bmp buttons or radio and
check buttons should be carefully specified in upper case
in the config attribute.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Bug # : 10033C
Description : MOUSE BEHAVIOR RESOURCE IN FGLPROFILE ARE CASE SENSITIVE
Full description : gui.key.0.translate, gui.key.click.right, and
gui.key.doubleClick.left resources in fglprofile are case
sensitive.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Bug # : 10033D
Description : THE RESOURCE ARE CASE SENSITIVE IN FGLPROFILE
Full description : The resources specifying the cut, past, copy and interrupt
keys have to be set with case sensitive value: "F5" may
work but "f5" may not.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Bug # : 10033E
Description : THE WAY TO CHANGE CONTROL FRAME LABELS ARE CASE SENSITIVE
Full description : The name of the key for changing the label of a button
located in the control frame with fgl_keysetlabel or
dialog.keysetlabel or with the key section or attribute in
a form specification file should be completely case
insensitive.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Bug # : 10034
Description : 4GL SOURCE FILES WRITTEN WITH MS NOTEPAD CAN NOT BE
COMPILED
Full description : You can not compile a 4GL source file created with MS
NOTEPAD. At compile time you always have an error at the
last line before the "end main" statement.
Appeared the : 10/05/1999
Apparition version : 2.91.007
Bug # : 10034B
Description : PER FORM FILES WRITTEN WITH MS NOTEPAD CAN NOT BE COMPILED
Full description : You can not compile a per form file created with MS
NOTEPAD. At compile time you always have an error at the
last line.
Appeared the : 19/05/1999
Apparition version : 2.91.007
Bug # : 13004
Description : OPEN CURSOR WITH REOPTIMIZATION
Full description : Clause "WITH REOPTIMIZATION" produces a compilation error
when used in an OPEN cursor instruction.
Appeared the : 10/05/1999
Apparition version : 2.91.010
Bug # : 13005
Description : FOREACH CURSOR WITH REOPTIMIZATION
Full description : Clause "WITH REOPTIMIZATION" is not recognized when used in
a FOREACH instruction. Gives a compilation error
Appeared the : 10/05/1999
Apparition version : 2.91.010
Bug # : 13006
Description : CONNECT TO DEFAULT DOES NOT SUPPORT WITH CONCURRENT
TRANSACTION OPTION
Full description : The CONNECT statement does not support WITH CONCURRENT
TRANSACTION when using the "DEFAULT" keyword as database
name
Appeared the : 17/05/1999
Apparition version : 2.91.010
Bug # : 13007
Description : DECIMAL VALUES ARE TRUNCATED IN LOAD INSTRUCTION
Full description : When using the LOAD instruction, DECIMAL values are
truncated to the second decimal position : if the file has
value 615.768762, after loading, value 615.770000 is in the
database.
Appeared the : 18/05/1999
Apparition version : 2.91.013
Bug # : 16005
Description : YOU MUST BE THE OWNER OF THE FGLDIR DIRECTORY TO RUN IT FOR
THE FIRST TIME
Full description : After having installed a package you can not use for the
first time as a non-owner of the FGLDIR directory : because
after installation the LOCK directory is deleted : so when
you run something, the lock file is trying to be generated
and it can't if you do that as a user which the package
doesn't belong to (the one who installed the product)
Workaround : run for example rtsinstall as the owner to re-generate the
lock file before being able to use the package as another
user.
Appeared the : 03/05/1999
Apparition version : 2.91.007 ?
Bug # : 17001
Description : SYNTAX ERROR IN THE FGLPROFILE GIVES NOT A GOOD ERROR
MESSAGE AT EXECUTION
Full description : When you execute a program which uses its own fglprofile
and this fglprofile has a syntax error, you get the error :
syntax error b17001.prf(1): at gui ERROR(-6324):Can't load
customer profile 'b17001.prf' SYS ERROR(2):No such file or
directory This error "No such file or directory" is not
correct.
Appeared the : 05/05/1999
Apparition version : 2.91.007
Bug # : 7349
Description : FORMAT IN FORM IS NOT RESPECTED INSIDE A CONSTRUCT
Full description : If you declare a field ( for example a date ) inside a
form, inside a construct there is no control on the
validity of the format
Appeared the : 19/03/1999
Apparition version : 2.10.4c2
Bug # : 9094
Description : LET A DATETIME WITH A USING RUNS IN ERROR
Full description : LET DATETIME = DATETIME USING "&&" runs in error with
following message : A field in a datetime or interval is
out of range
Workaround : Remove the using.
Appeared the : 17/12/1998
Apparition version : 2.02.3b1
Bug # : 9124
Description : STARTING A 42R PROGRAM WHICH IS A NULL FILE DUMPS CORE ON
SUN BOXES
Full description : Running the command fglrun appl.42r where appl.42r is a
null file ( cat /dev/null > appl.42r ) dumps core on sun
boxes. On other platforms it warns : File '(null)': Bad
magic: Code can't run with this p-code machine.
Workaround : Run the right 42r file or link it again.
Appeared the : 20/04/1999
Apparition version : 2.10.4c2
Bug # : 5274B
Description : PROBLEM WITH PAGE TRAILER AND SEMI-COLON WITH
DBPRINT=FGLSERVER
Full description : if the PAGE TRAILER finishes with an instruction like PRINT
"blabla"; and you have DBPRINT=FGLSERVER or you print to
the screen, you don't get "Page Trailer" at the end of the
page.
Workaround : Work around: use TOP OF PAGE instruction in OUTPUT FORMAT
Appeared the : 29/04/1999
Apparition version : 2.91.008
Bug # : 7266
Description : COMMENT LINE AND INPUT ON THE SAME LINE, ENTRY IS INVISIBLE
Full description : If the comment line is on the same line as the field of an
input, the entry stays invisible ( the comment line is over
the entry )
Appeared the : 04/03/1998
Apparition version : 2.02.1e6k3
Bug # : 9127
Description : DDE - THE PROGRAM DUMPS CORE AT THE SECOND DDEPEEK COMMAND
Full description : The program dumps core at the next DDE command after a
ddepeek command
Appeared the : 06/05/1999
Apparition version : 2.10.4c2
Bug # : 12010
Description : MIX WITH 2 SUCCESSIVE REPORTS AT DISPLAY
Full description : When doing a START REPORT of a first report, finishing it
and immediately STARTing a second report, the display is a
mix and keeps information from the first report . This only
happens on display, with a START REPORT to file it works
well
Appeared the : 19/06/1998
Apparition version : 2.02.1e6l6
Bug # : 12032
Description : ASCII CODE IS DISPLAYED TYPING GRAPHICAL CHARACTERS WITH
ALT + CHAR CODE
Full description : When typing a special character in a dialog field with ALT
+ , the typed ASCII code appears before the
special character.
Appeared the : 11/03/1999
Apparition version : 2.10.4c2
Bug # : 12032
Description : ASCII CODE IS DISPLAYED TYPING GRAPHICAL CHARACTERS WITH
ALT + CHAR CODE
Full description : When typing a special character in a dialog field with ALT
+ , the typed ASCII code appears before the
special character.
Appeared the : 11/03/1999
Apparition version : 2.10.4c2
Bug # : 5273C
Description : PRINT "BLABLA"; SKIP TO TOP OF PAGE GIVES A BAD RESULT ON
THE STANDARD OUTPUT
Full description : print "blabla"; skip to top of page after doing the last
page trailer, Informix gives a blank line but not FourJs.
Appeared the : 19/05/1999
Apparition version : 2.91.012
Bug # : 5273D
Description : PRINT "BLABLA"; IN PAGE TRAILER GIVES A BAD RESULT ON THE
STANDARD OUTPUT
Full description : print "blabla"; skip to top of page print "trailer"; FourJs
does not display 4 blank lines and the line "trailer" at
the end of the page. When you PRINT to a file, the result
is correct.
Appeared the : 19/05/1999
Apparition version : 2.91.012
Bug # : 4024
Description : NO DATA IS SENT TO THE PRINTER
Full description : When a report to printer is made. No data is sent to
printer. The wtk receive from the runner "report begin",
"report end" and no data between.
Appeared the : 08/06/1999
Apparition version : 2.91.019
Correction version : 2.91.020
Bug # : 7344
Description : CANNOT INTERRUPT A DIALOG
Full description : On Linux using glib 2.0.6 only, in graphic and ASCII mode,
you cannot interrupt a dialog but the variable int_flag is
set to TRUE. You can interrupt a sleep
Appeared the : 16/02/1999
Apparition version : 2.10.4c2
Correction version : 2.91.020
Bug # : 4019
Description : FGLFORM CORE DUMP ON SCREEN ARRAY
Full description : If you specify a non existing field in the screen record,
the form compiler generates a core dump on Unix and GPF on
NT instead of an error message.
Appeared the : 08/01/1999
Correction version : 2.91.019
Bug # : 5370
Description : DEFAULT MONEY IS NOT TRANSLATED CORRECTLY IN REPORT IN
C-CODE
Full description : DEFAULT MONEY IS NOT TRANSLATED CORRECTLY IN REPORT IN
C-CODE. If you look inside the temporary table created for
the report (use FGLSQLDEBUG=1), you see that the MONEY is
declared MONEY(16,255)
Appeared the : 31/05/1999
Apparition version : 2.91.016
Correction version : 2.91.019
Bug # : 5375
Description : IF YOU DO A PROMPT IN TERMINAL MODE AND EXIT PROGRAM, THE
TERMINAL IS NOT RESET
Full description : If you do a prompt in terminal mode and exit the program,
the terminal is not reset
Appeared the : 03/06/1999
Apparition version : 2.91.018
Correction version : 2.91.019
Bug # : 6510C
Description : A REPORT TO FILE WITH FORMAT EVERY ROW GENERATES A
COREDUMP
Full description : EVERY ROW used as FORMAT part of a REPORT shows the values
of all transmitted parameters and therefore is very often
used for debugging purposes (in absence of an interactive
debugger...). Unfortunately with F4GL it doesn't work and
dumps core when you send the report to a file.
Appeared the : 03/06/1999
Apparition version : 2.91.012
Correction version : 2.91.019
Bug # : 7079
Description : WITHOUT CALLING SET_COUNT A LINE IS DISPLAYED WHEN EXITING
A DISPLAY ARRAY
Full description : Without calling set_count a line is displayed when exiting
a display array
Appeared the : 08/12/1998
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 7272
Description : TOO LARGE VALUES IN DECIMAL ARE NOT CONTROLLED AND GIVE
WRONG RESULTS
Full description : Giving a value too big to a decimal gives no error and
displays bad values. With Informix 4.1, an error appears :
Decimal or money value exceeds maximum precision. With
Informix 7.x, no error appears, but values are null.
Workaround : set in fglprofile fglrun.checkDecimalPrecision=1 In this
case, fglrun reacts like Informix 7.x: no error appears
but values are NULL.
Appeared the : 25/03/1998
Apparition version : 2.02.1e6k3
Correction version : 2.91.016
Bug # : 7272B
Description : TOO BIG VALUE IN DECIMAL IS NOT CONTROLLED
Full description : Giving a value too big to a decimal gives no error. You
must insert in your 4GL the statement "WHENEVER ANY ERROR
..." to see the errors.
Workaround : set in fglprofile fglrun.checkDecimalPrecision=1 In this
case, fglrun reacts like Informix 7.x: the errors appears
and the values are NULL.
Appeared the : 31/05/1999
Apparition version : 2.02.1e6k3
Correction version : 2.91.016
Bug # : 7273B
Description : SETCURSOR DOESN'T WORK IN BEFORE FIELD
Full description : If the function dialog.setcursor is used inside a before
field, the cursor stays on the first position in the
current field.
Appeared the : 17/05/1999
Apparition version : 2.10.4c2
Correction version : 2.91.016
Bug # : 7275
Description : CALCULATION GIVES A BAD RESULT INSTEAD OF A NULL VALUE
Full description : By a simple calculation, F4GL gives a result not null but
Informix gives a null value because of the lack of
precision place. This can give big calculation errors.
Appeared the : 22/04/1998
Apparition version : 2.02.1e6k3
Correction version : 2.91.016
Bug # : 7275B
Description : CALCULATION GIVES A RESULT INSTEAD OF ERROR
Full description : By a simple calculation, F4GL gives a result not null and
Informix gives an error because of the lack of precision
place and a null value. This can give big calculation
error. You must insert in your 4GL the statement
"WHENEVER ANY ERROR ..." to see the errors.
Appeared the : 31/05/1999
Apparition version : 2.02.1e6k3
Correction version : 2.91.016
Bug # : 7331
Description : CLOSE CURRENT FORM INSIDE AN INPUT GIVES CORE DUMP
Full description : Inside an input, if you close the current form in a
trigger and open another form with an input, it gives a
core dump on SUN. On Linux, it works on ASCII,
but crashes on GUI mode.
Appeared the : 20/11/1998
Apparition version : 2.02.3b1
Correction version : 2.91.019
Bug # : 7349
Description : FORMAT IN FORM IS NOT RESPECTED INSIDE A CONSTRUCT
Full description : If you declare a field ( for example a date ) inside a
form, inside a construct there is no control on the
validity of the format
Appeared the : 19/03/1999
Apparition version : 2.10.4c2
Correction version : 2.91.016
Bug # : 7350
Description : EXIT CONSTRUCT DISTURBS GOING ON SAME CONSTRUCT A SECOND
TIME
Full description : After an exit construct, going a second time in the same
construct, given characters are not visible if characters
were entered in the same field the first time in the
construct (only with tcl interface 2)
Appeared the : 13/04/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 7351
Description : INSERTING A ROW IN AN INPUT ARRAY GIVES A REVERSE LINE IN
THE 1ST AND LAST LINE
Full description : When an insert is done inside an input array, the reverse
line is on the new line for the first field and on the
last line for the second field when, in the form, fields
have the attribute reverse.
Appeared the : 14/04/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 7353
Description : BOX MADE WITH SEMI-GRAPHIC CHARACTERS IS NOT FULL
Full description : If a box is made by using semi-graphic characters in the
form, the lower right corner is not fully drawn
Appeared the : 23/04/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 7356
Description : CARRIAGE RETURN ON TEXT FIELD IS NOT DISPLAYED
Full description : IF a text field contains carriage return, by displaying it
the carriage return is replaced by the character "?"
Appeared the : 11/05/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 7359
Description : CONNECTION TO DEFAULT WITH CONCURRENT TRANSACTION
Full description : The command CONNECT TO DEFAULT WITH CONCURRENT TRANSACTION
is not accepted at the compilation.
Appeared the : 21/05/1999
Apparition version : 2.91.013
Correction version : 2.91.019
Bug # : 9033
Description : PROBLEM WITH REVERSE DISPLAY
Full description : With F4GL, the first input or Display holds the reverse
attribute and we can not switch it in normal mode. With
this syntax the problem occurs only in graphical mode.
Also detected with DISPLAY ARRAY.
Appeared the : 21/01/1998
Apparition version : 2.02.1e6k3
Correction version : 2.91.019
Bug # : 9091
Description : IN ASCII MODE WHEN LEAVING A MENU IT IS STILL DISPLAYED
Full description : In ASCII mode when living a second level menu to a first
level shorter menu, the end of the second level menu still
on the screen.
Appeared the : 11/12/1998
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 9102
Description : ASCII MODE, THE MENU IS NOT REFRESHED WHEN COMING BACK
FROM AN OTHER MENU
Full description : In ASCII mode, there are trailing displays on the menu
line when coming from a second menu and when the menu
line is not the first line.
Appeared the : 19/01/1999
Apparition version : 2.02.3b1
Correction version : 2.91.019
Bug # : 9105
Description : Q AND D FLAGS IN SCREEN SECTION DON'T DRAW A CORNER
Full description : q and d flags in screen section of a form file don't draw
a corner like Informix 4GL does. This happened only in GUI
mode.
Appeared the : 28/01/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 9113
Description : TRAILING ZEROS IN FLOAT DATA TYPE FIELDS
Full description : With only some values like 1.11 in float fields, the
display will be shown like 1.110000000. Other values like
0.06 are shown like 0.06. It depends also on the
computation you do on the field, 9.999 + 0.001 will
display 10.0000000000 but 10.000 + 0.000 will display
10.0
Appeared the : 16/03/1999
Apparition version : 2.10.4c2
Correction version : 2.91.016
Bug # : 9118
Description : THE PAGEDOWN KEY DOESN'T WORK IF THERE IS A NEXT FIELD
Full description : The pagedown key scrolls only one line down if there is a
next field command in the input array. Informix 4GL scroll
X+1 screen record lines.
Workaround : Check if pagedown is pressed and move the current line
with the function dialog.setcurrline.
Appeared the : 24/03/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 9124
Description : STARTING A 42R PROGRAM WHICH IS A NULL FILE DUMPS CORE ON
SUN BOXES
Full description : Running the command fglrun appl.42r where appl.42r is a
null file ( cat /dev/null > appl.42r ) dumps core on sun
boxes. On other platforms it warns : File '(null)': Bad
magic: Code can't run with this p-code machine.
Appeared the : 20/04/1999
Apparition version : 2.10.4c2
Correction version : 2.91.016
Bug # : 10031
Description : MENU BUTTON LABEL IS NOT CHANGED ACCORDING ITS VARIABLE
CONTENTS IN GUI MODE
Full description : In the graphical mode the menu button label doesn't
dynamically change according to the variable content. The
ASCII mode works well.
Workaround : Add the next three lines to refresh the labels of the menu
: HIDE OPTION SHOW OPTION NEXT
OPTION The two first statements refresh the
labels of the menu buttons and the last one keep the
focus on the current menu button.
Appeared the : 22/01/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 10033B
Description : THE KEY RETURNED BY CANVAS, BMP, BUTTONS, RADIO/CHECKS IS
CASE SENSISTIVE
Full description : The key returned by the canvas bmp buttons or radio and
check buttons should be carefully specified in upper case
in the config attribute.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Correction version : 2.91.019
Bug # : 10033C
Description : MOUSE BEHAVIOR RESOURCE IN FGLPROFILE ARE CASE SENSITIVE
Full description : gui.key.0.translate, gui.key.click.right, and
gui.key.doubleClick.left resources in fglprofile are case
sensitive.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Correction version : 2.91.019
Bug # : 10033D
Description : THE RESOURCE ARE CASE SENSITIVE IN FGLPROFILE
Full description : The resources specifying the cut, past, copy and interrupt
keys have to be set with case sensitive value: "F5" may
work but "f5" may not.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Correction version : 2.91.019
Bug # : 10033E
Description : THE WAY TO CHANGE CONTROL FRAME LABELS ARE CASE SENSITIVE
Full description : The name of the key for changing the label of a button
located in the control frame with fgl_keysetlabel or
dialog.keysetlabel or with the key section or attribute in
a form specification file should be completely case
insensitive.
Appeared the : 11/05/1999
Apparition version : 2.91.007
Correction version : 2.91.019
Bug # : 10034
Description : 4GL SOURCE FILES WRITTEN WITH MS NOTEPAD CAN NOT BE
COMPILED
Full description : You can not compile a 4GL source file created with MS
NOTEPAD. At compile time you always have an error at the
last line before the "end main" statement.
Appeared the : 10/05/1999
Apparition version : 2.91.007
Correction version : 2.91.016
Bug # : 10034B
Description : PER FORM FILES WRITTEN WITH MS NOTEPAD CAN NOT BE COMPILED
Full description : You can not compile a per form file created with MS
NOTEPAD. At compile time you always have an error at the
last line.
Appeared the : 19/05/1999
Apparition version : 2.91.007
Correction version : 2.91.016
Bug # : 11017
Description : A PARTICULAR WAY TO DISPLAY A SIMPLE QUOTE DOES NOT WORK
WITH F4GL
Full description : The F4GL compiler does not accept this syntax : DISPLAY
'bla bla bla '' bla bla bla'
Appeared the : 24/06/1998
Correction version : 2.91.019
Bug # : 12008
Description : FGLFONTSEL DOESN'T START WITH RUNTIME
Full description : When running fglfontsel in subdirectory $FGLDIR/bin,
following error message appears : sh: xlsfonts: not found
program stopped at "fglfontsel.4gl", line number 91.
FORMS statement error number -1110. Form file not found.
Appeared the : 08/06/1998
Apparition version : 2.02.1e6l7
Correction version : 2.91.016
Bug # : 12008B
Description : CHANGE FONT BUTTON IN FGLFONTSEL HAVE NO EFFECT
Full description : "Change Font" have no effect
Appeared the : 31/05/1999
Apparition version : 2.91.015
Correction version : 2.91.016
Bug # : 12010
Description : MIX WITH 2 SUCCESSIVE REPORTS AT DISPLAY
Full description : When doing a START REPORT of a first report, finishing it
and immediately STARTing a second report, the display is a
mix and keeps information from the first report . This
only happens on display, with a START REPORT to file it
works well.
Appeared the : 19/06/1998
Apparition version : 2.02.1e6l6
Correction version : 2.91.018
Bug # : 12045
Description : 42M FILENAMES ARE WRITTEN WITH DIRECTORY PATH IN THE 42R
FILE
Full description : Compile 2 modules with fgl2p by using a directory path to
the source files and move the 42m files into a different
directory. Create the 42r module with the path to this new
directory. The compilation works fine, but the program
cannot be executed because the original paths are used in
the 42r file. Setting FGLLDPATH correctly does not help.
Appeared the : 28/05/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 13004
Description : OPEN CURSOR WITH REOPTIMIZATION
Full description : Clause "WITH REOPTIMIZATION" produces a compilation error
when used in an OPEN cursor instruction.
Appeared the : 10/05/1999
Apparition version : 2.91.010
Correction version : 2.91.016
Bug # : 13005
Description : FOREACH CURSOR WITH REOPTIMIZATION
Full description : Clause "WITH REOPTIMIZATION" is not recognized when used
in a FOREACH instruction. Gives a compilation error.
Appeared the : 10/05/1999
Apparition version : 2.91.010
Correction version : 2.91.016
Bug # : 13006
Description : CONNECT TO DEFAULT DOES NOT SUPPORT WITH CONCURRENT
TRANSACTION OPTION
Full description : The CONNECT statement does not support WITH CONCURRENT
TRANSACTION when using the "DEFAULT" keyword as database
name
Appeared the : 17/05/1999
Apparition version : 2.91.010
Correction version : 2.91.016
Bug # : 13007
Description : DECIMAL VALUES ARE TRUNCATED IN LOAD INSTRUCTION
Full description : When using the LOAD instruction, DECIMAL values are
truncated to the second decimal position : if the file has
value 615.768762, after loading, value 615.770000 is in
the database.
Appeared the : 18/05/1999
Apparition version : 2.91.013
Correction version : 2.91.016
Bug # : 13008
Description : SELECT IN SQL BLOCK FILLS A RECORD WITH INCORRECT VALUES
Full description : When doing an INSERT in static SQL using an array,
followed by a SELECT in an SQL block, the values fetched
into the destination record differ from the inserted
values. The problem appears only when using an array of
record in a static INSERT and when listing all INTO
members of the destination record in the SELECT, when
using a simple record or when doing the INSERT in an SQL
block or when using a start with the destination record
(INTO dest_rec.*), it works fine.
Appeared the : 26/05/1999
Apparition version : 2.91.015
Correction version : 2.91.016
Bug # : 13009
Description : THE INTO CLAUSE IS NOT SUPPORTED IN EXECUTE INSTRUCTION
Full description : The new version of the compiler should support an INTO
clause with the EXECUTE instruction. Gives a compilation
error for now.
Appeared the : 26/05/1999
Apparition version : 2.91.015
Correction version : 2.91.016
Bug # : 13010
Description : CURSOR MOVES ONE ROW UP IN INPUT ARRAY WHEN CANCEL INSERT
IS RAISED ON LAST ROW
Full description : When executing a CANCEL INSERT on the last row in an INPUT
ARRAY, the cursor jumps to the previous row in the screen
array. The cursor should stay on the last row.
Appeared the : 26/05/1999
Apparition version : 2.91.015
Correction version : 2.91.019
Bug # : 13012
Description : THE DORMANT OPTION OF SET CONNECTION HAS NO EFFECT
Full description : When executing a SET CONNECTION TO "C" DORMANT, the
connection should become inactive but it is still possible
to execute SQL statements.
Appeared the : 26/05/1999
Apparition version : 2.91.015
Correction version : 2.91.016
Bug # : 13013
Description : COMMENTS ARE NOT CONVERTED TO BLANKS IN SQL BLOCKS
Full description : In SQL Blocks, comments between {} must be converted to
one blank character to allow the programmers to write :
SELECT{}colname{}FROM{}tabname.
Appeared the : 31/05/1999
Apparition version : 2.91.014
Correction version : 2.91.016
Bug # : 13014
Description : ERRORLOG() WRITES TWO LINES IN LOG FILE WITH C CODE
Full description : When compiling in C-Code, errorlog( ) functions writes two
times the same row into the log file.
Appeared the : 31/05/1999
Apparition version : 2.91.010
Correction version : 2.91.016
Bug # : 16005
Description : YOU MUST BE THE OWNER OF THE FGLDIR DIRECTORY TO RUN IT
FOR THE FIRST TIME
Full description : After having installed a package you can not use for the
first time as a non-owner of the FGLDIR directory :
because after installation the LOCK directory is
deleted : so when you run something, the lock file is
trying to be generated and it can't if you do that as a
user which the package doesn't belong to (the one who
installed the product)
Appeared the : 03/05/1999
Apparition version : 2.91.007 ?
Correction version : 2.91.016
Bug # : 16009
Description : A SKIP TO TOP OF PAGE IN A BEFORE GROUP MAKES THE FIRST
DATA DISPLAY ON 2ND PAGE
Full description : If you use a "skip to top of page" in a "before group xxx"
in a report, it will make a page skip after the first page
header ("first page header"), and will go to second page ,
and print "page header" : so the first data will be printed
on the second page ...
Appeared the : 26/05/1999
Apparition version : 2.91.007
Correction version : 2.91.019
Bug # : 16010
Description : RESULT OF A SELECT ... FROM .. ORDER BY XXX[] IS
NOT RIGHT
Full description : In comparing the result of a " select xxxx from yyy order
by xxxx[]" between dbacess and the runner, notice
that the runner does not order the data like expected.
Appeared the : 02/06/1999
Apparition version : ?
Correction version : 2.91.019
Bug # : 16010B
Description : RESULT OF A SELECT ... FROM .. GROUP BY XXX[] IS
NOT RIGHT
Full description : In comparing the result of a " select xxxx from yyy group
by xxxx[]" between dbacess and the runner, notice
that the runner does not order the data like exepected.
Appeared the : 02/06/1999
Apparition version : ?
Correction version : 2.91.019
Bug # : 17001
Description : SYNTAX ERROR IN THE FGLPROFILE GIVES NOT A GOOD ERROR
MESSAGE AT EXECUTION
Full description : When you execute a program which uses its own fglprofile
and this fglprofile has a syntax error, you get the
error : syntax error b17001.prf(1): at gui
ERROR(-6324):Can't load customer profile 'b17001.prf'
SYS ERROR(2):No such file or directory This error
"No such file or directory" is not correct.
Appeared the : 05/05/1999
Apparition version : 2.91.007
Correction version : 2.91.016
Bug # : 17003
Description : A DISPLAY DOES NOT REFRESH THE FIELD VALUES IN A FORM
Full description : In an input, if you modified values displayed in a form
field and quit the input with an interrupt, the display
executed just after the input doesn't refresh the values.
Workaround : Some information: this problem only appears with local
editing (you can disable it by gui.local.edit=0 in
fglprofile). Because for optimization, only modified
fields are transmit by the runner, the GUI client send
now the value of the modified field even if a interrupt
appears. Because of some other optimization, we cannot
transmit a Out of band datas and the application is not
stopped if no defer interrupt is defined (bug 17003B).
Appeared the : 04/06/1999
Apparition version : 2.10.4c2
Correction version : 2.91.019
Bug # : 5371
Description : ONLY KEYS FROM THE KEYBOARD MUST BE BUFFERED
Full description : Only keys from the keyboard must be buffered if the client
waits. Clicks on buttons except interrupt should do
nothing when the wait of the client finish (the hour
glass disappears). The same for scrollbar, click on
field, etc...
Appeared the : 01/06/1999
Apparition version :
Correction version : 3.00.1e
Bug # : 5372
Description : SELECTION ON THE FIRST FIELD OF DISPLAY ARRAY ALWAYS
BEGINS TO THE FIRST CHAR
Full description : Selection (cut & Paste) on the first field of a display
array always begins to the first character.
Appeared the : 03/06/1999
Apparition version :
Correction version : 3.00.1e
Bug # : 5373
Description : FOLDERS ARE NOT DESTROYED WITH A CLEAR WINDOW
Full description : Folders are not destroyed with a clear window. If you
click on it, you can have tcl error if the form was
closed
Appeared the : 03/06/1999
Apparition version :
Correction version : 3.00.1e
Bug # : 5373B
Description : FOLDERS ARE NOT DESTROYED WITH A NEW FORM IN A WINDOW
Full description : Folders are not destroyed with a clear window with a new
form in a window. If you click on it, you can have tcl
error if the form was closed
Appeared the : 03/06/1999
Apparition version :
Correction version : 3.00.1e
Bug # : 5374
Description : TOO LONG TITLES IN FOLDERS ARE NOT CONTROLLED
Full description : Too long titles in folders are not controlled: must be
truncate.