home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: InfoMgt
/
InfoMgt.zip
/
dbup208.zip
/
FIXLIST.TXT
< prev
next >
Wrap
Text File
|
1999-09-02
|
17KB
|
429 lines
DBExpert(tm) Relational Database for OS/2 from Sundial Systems
List of Problem Fixes (FIXLIST.TXT)
September 1999
This file contains a brief listing of each problem which has been fixed in
DBExpert since the release of Version 2.0.
The following problems were fixed in DBExpert version 2.0.8:
* Object references to values on current report (eg. ActiveReport:field)
not working
* Object references to attributes of forms and reports (eg.
ActiveForm.Title) not working
* Two digit dates not displayed correctly once system clock rolls over to
2000
* Margins on reports reset to default unless identical printer name is
found
* Unclear error displayed when attempting to design a table, query,
report, or macro and the corresponding design is already open
* Can't close table or form when current record contains invalid data
* Can't set "keep together" attribute for report headers and footers
* Report footer partially overlaps page footer on some reports
* OnFormat and OnPrint events in group headers/footers on reports still
invoked even after such a header or footer is removed from the report
* Query Designer will not display totals line for any Insert query
* Very large or very small numbers (more than 10 digits) returned in
total queries (eg, SUM, AVG, etc) over a dBase-style table are not
displayed correctly
* Records->Refresh menu option on spreadsheets and forms not attempting
to keep spreadsheet/form on same record number
* dbeRequery function not attempting to keep spreadsheet/form on same
record number
* Find on current field in backward direction does not find record in
certain situations if any record has been updated or inserted since
the form or spreadsheet has been opened
* Form events with macro calls sometimes skipped when rapidly clicking
VCR controls on form
* Having a subform as the first control in the tab order of a form causes
SYS3175 trap when form is opened
* Clicking on subform which is not a tabstop causes hang if subform is
in form view
* Subform which is not a tabstop does not initially display correctly if
subform is in spreadsheet view
* Some simple WHERE clauses in the Filter parameter of the dbeQueryCount
function (and other similar functions) cause an erroneous error message
* Print preview window does not automatically become the active window
if the report is based on a query which requires user parameters
The following problems were fixed in DBExpert version 2.0.7:
* Parentheses around expression in query condition for individual field
causes SYS3175 trap
* Listbox or Combobox displaying field list doesn't produce selected value
* Find on all fields for start or part of value finds wrong record in
certain situations
* Find on current field finds wrong record in certain situations
* Find on current field sometimes fails to find record
* Case sensitive find for start or part of value sometimes displays an
erroneous error message
* Find Next on current field stays on same record in certain situations
* Memory leaks when closing a table, query or form
* Memory leaks when processing SQL statements
* Memory leak when closing query designer
* Font and font size not correct when printing subreports without a source
* dbeCharToTime (and related automatic conversions) returns null for
"12:00:00"
* dbeCharToTimestamp (and related automatic conversions) do not rollover
"24:00:00" (and similar values) to the next day
* Pie graphs sized much smaller than expected
* Blank lines ignored (collpased) when printing MLE fields
* MLE fields not positioned correctly in second and subsequent columns
of multicolumn report
* Can't update/create records in a DB2 table where a Counter field is the
primary key
* Can't update/create records in a DB2 table using numbers containing
decimal commas (even when the system decimal character is set to comma)
* Can't set a value to NULL in an Update query
* Exported column names always separated by commas regardless of which
delimiter is specified
* Exported column names always appear in delimited format even when fixed
format is specified
* Values exported in fixed format are not truncated if they are too long
* Printing to an unavailable printer displays an erroneous error message
* Mnemonic (accelerator) characters not working on form controls
* OnExit event not working in spreadsheet views of forms
* dbeRunSQL calls with Delete, Insert, or Update queries sometimes fail
with an erroneous "all columns are read only" condition
* Seemingly random "column is read only" errors when deleting, inserting,
or updating records under some conditions
The following problems were fixed in DBExpert version 2.0.6:
* On Push event not working for radio buttons, toggle buttons, and
checkboxes
* Dates entered in the year 1900 (only) converted to the year 2000
* DB2 rows containing blank (i.e., space) values for NOT NULL fields
cannot be edited
* Subreports randomly do not print on particular reports
* Horizontal scroll bar is disabled for tables with a large number of
columns
* Mouse click to select item in combobox causes form to no longer be
active
* Printer setup dialog often shows name of default printer even if another
is used
* Print dialog does not show correct printer name if printer is changed
* Queries which result in long SQL statements (>5000 characters) often
trap
* When used in a macro, the dbeRandom function returns the same sequence
of numbers each time the macro is run
The following problems were fixed in DBExpert version 2.0.5:
* Canceling the printing of certain reports causes continuous loop
* Default positioning of tall forms sometimes places top of form off
screen
* Radio buttons in a group on a form are not properly reset when moving
from one record to another
* The dbeInt function returns an empty string for values between -1 and 1
* The dbeInt function returns the "truncation" rather than "largest
integer less than" for negative numbers (e.g., -3 rather than -4 for
-3.5)
* The dbeInt function does not work when the system's decimal character
is set to anything other than a period (.)
* The dbeRound function returns an empty string for some values
* The dbeRound function does not return the correct value when the
leftmost digit requires rounding (such as .96 being rounded to 1)
* The dbeRound function does not work when the system's decimal character
is set to anything other than a period (.)
* When called from REXX, the dbeRound function modifies the number passed
to it as a parameter
* Implied rounding using a format string (such as ##0.00) sometimes
produces the wrong value (typically truncated rather than rounded)
* Percentage-style formatting (such as ##%) does not work when the
system's decimal character is set to anything other than a period (.)
* Computations (such as Quantity * Price) in queries, on forms, or on
reports that involve fractional values retrieved from a table do not
produce the correct value when the system's decimal character is set to
anything other than a period (.)
* Passing the literal value "true" in a REXX macro to any dbe function
requiring a true or false value generally causes the value to be
interpreted as false (rather than true)
* The state of the vertical scrollbar on a spreadsheet view being used as
a subform is not properly set when moving from record to record on the
form
* Vertical scrollbars on spreadsheet views containing no records are
enabled even though they should not be
* If a problem is encountered when deleting a table, the error message is
not usually displayed
* If a problem is encountered while deleting the physical table for a
dBase-style table, an incorrect error message is displayed
* If a problem is encountered while attaching a dBase-style table, an
incorrect error message is displayed in some cases
* Using Save in the Table Designer to change the definition of an attached
dBase-style table causes the table to be moved from its original
location to the directory where DBExpert is installed
* Using Save in the Table Designer causes the the physical name of a
dBase-style table to be changed to a new name generated by DBExpert
* The dbeClose function displays an error message when it is used to close
something (such as a specific form) that is not open
* Attempting to use a dBase-style table immediately after using the Change
Physical Table option sometimes produces an erroneous "information
record locked" error
* Calling the dbeExit function from a macro randomly causes SYS3175 traps
* The dbeCloseActiveWindow function does not work with some windows
(particularly forms)
* If a Date field in a table is set to Long Date format, values in the
field cannot be entered or edited correctly (on the spreadsheet directly
or on a form using the table)
* If a Timestamp field in a table is set to Long Date or Long Date/Time
format, values in the field cannot be entered or edited correctly (on
the spreadsheet directly or on a form using the table)
* Macro parameters could not contain blanks (spaces)
* Blanks (spaces) could not be used to delimit multiple macro parameters
even if the macro was expecting blanks to be used this way
The following problems were fixed in DBExpert version 2.0.4:
* Add, delete, or update of dBase records randomly causes SYS3171 trap in
QEUTL04.DLL, particularly when multiple records are involved
* Form without entry fields causes SYS3175 trap when switched to
spreadsheet view
* Report with only static fields (i.e., no source table or query) causes
SYS3175 trap on print
* Import of duplicates to table with unique key causes loss of records
following first duplicate
* Adding unique key to table with duplicates causes loss of
records following first duplicate
* The dbeTimestampToTime function always returns the same (incorrect) value
* Timestamp values cannot be imported correctly
* Time values cannot be imported correctly
* Fixed format import requires an extra column width (e.g., 0;) be prepended
to the list of column widths
* Fixed format import repeats the final field content if record is too
short
* Fixed format export hangs (or otherwise works incorrectly) in most cases
* Trying to close DBExpert from the OS/2 Window List doesn't do anything
* Form or spreadsheet view cannot be refreshed after a record locked
condition is returned from DB2
* Form or spreadsheet view cannot be closed after a record locked condition
is returned from DB2
* "Query not open error" displayed when previewing report containing no
data
* Records containing newline characters inside quoted fields cannot be
imported
* Error displayed when using dbeSendKeys to send F10, F11, or F12
* Tab, enter, or backspace not necessarily sent correctly by dbeSendKeys
* Counter field values not set when importing records
* Counter field values not set when counter field added to existing table
* Vertically stacked MLEs on reports sometimes cause unnecessary white space
* dbeOpen on a form or table that is already open but minimized does not
make the form visible
* Query Designer will not display totals line for any Make Table query
* When NUMLOCK is on, the decimal point key on the numeric pad does not
work in forms
* dBase table cannot be attached if drive letter portion of the filename is
in lower case
* Float values in table from DB2 V2 take on type of preceding column (Note:
to correct the problem for an existing table, the table must be
reattached.)
* 00 entered for a year is interpreted as current year rather than 1900
* Dates in 2000 and beyond displayed as 19xx even when a four digit year
format is specified
* Fractional seconds are not displayed even with "ss.ss" in format string
* Records with timestamps set using DB2 CURRENT TIMESTAMP can't be updated
* Find, when matching the entire contents of a single field, generally
does not work on a table with indices
* Find, when matching the entire contents of any field, sometimes matches
unexpected records
* Numbers between 0.0 and 0.1 incorrectly formatted when returned from DB2
(which may then cause incorrect error messages about the record being
locked or changed by another user)
The following problems were fixed in DBExpert Version 2.0.3:
* Pressing a key or clicking a mouse button on client area of form while
form is loading records from the data source causes SYS3175 trap
* Opening a second form in the 'Before Open' event of a form causes SYS3175
trap
* Numbers sometimes displayed incorrectly if the format string for the
number caused the value to be rounded
* Manually editing SQL for queries containing more than one table sometimes
causes SYS 3175 trap or sometimes results in loss of changes made during
editing
* Switching from the form to the spreadsheet view causes a SYS3175 trap if
the cursor is on a field in a subform
* Switching from spreadsheet view to form view causes a SYS3175 trap if an
error occurs while opening the data source for the form
* Calling the dbeRequeryControl() for a list or combo box during an event
causes a SYS3175 trap if the control has not finished loading its initial
list of records.
* Insert queries that try to insert a calculated date field into a date
field of the destination table do not work correctly
* Insert queries do not properly set any counter field values of the
inserted records.
* Keyboard and mouse focus does not properly switch to the second form when
a double-click event on one form opens another form.
* Subreports sometime do not print correctly.
The following problems were fixed in DBExpert Version 2.0.2:
* Unnecessary reconnection to Oracle server every time an Oracle table is
opened.
* Insert queries do no properly handle inserting data from a text or memo
field into a shorter text field.
* Import sometimes causes a SYS3175 trap.
The following problems were fixed in DBExpert Version 2.0.1:
* dbeUndo() function does not correctly undo changes made to fields and
records on forms, tables, or queries.
* Applications on drive A: and on network directories specified by just
the drive letter cannot be created or opened.
* Table in a directory has a '.' in the name (e.g., AUG.95) cannot be
attached.
* On reports, =dbeCount(fieldname) returned 1 more than actual count in
group footer sections after the first group footer.
* Tab key moves keyboard focus to subform after changing the value in a
field used to link the main form and the subform.
* Month and day names completely capitalized when using Dddd or Mmmm in the
format string.
* Last column of a Total query is duplicated when the last column uses one
of the total functions (SUM, COUNT, MIN, MAX, AVG).
* Calling dbeExit() from a button's On Push attribute causes SYS3175 trap.
* Performing operations on a form or table designs while the underlying
tables were being accessed in the background causes a SYS3175 trap.