DBExpert

DBExpert(tm) Relational Database for OS/2 from Sundial Systems List of Problem Fixes (FIXLIST.TXT) August 2000 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.9: * Executing large numbers of UPDATE (or INSERT) queries (possibly indirectly through other queries) gradually slows down query execution speed and eventually causes random failures, erroneous error messages, and possibly program lockup * Printing or previewing when a default printer is needed and no default printer is found displays a confusing error message * Import or export requests stop processing records if the main application window is minimized or hidden * Title bar of Preview window shows report name rather than report title * If an error occurs while running a macro on application startup, there is no obvious way to keep the application open * If the table names or totals options in the query designer are toggled on or off while some column attributes are being edited or selected, completing the entry or selection operation displays an erroneous error message * If a query is set to sort on other than the first column, that column becomes the first column once the query is saved and the query designer is closed * Reports with page footers which contain MLE fields which can grow, and which do grow to overlap past the bottom on the page, do not properly continue printing after the remainder of the footer is printed on the next page * Report detail sections which are set to "keep together" but which grow larger than the available page size never print * Query designer doesn't properly handle column inserts when multiple copies of the same table or query are used as sources in a single query * Queries involving conditions on identical column names from different tables may not properly associate the conditions with the correct table * Modifying column name of a table prevents any query that involves a join operation on that column from being opened in the query designer * MLE controls on forms do not visually refresh when their value is changed using dbeSetValue() * Alt+letter keyboard shortcuts do not work in the main portions of forms that contain a header and footer * Some report formatting options are not properly reset after a header or footer is removed from a report * Export improperly also lists INSERT, UPDATE, DELETE, and MAKE TABLE queries as possible sources (rather than only tables and SELECT queries) * dbeInt() returns incorrect value for 0 or any negative whole number * dbeSubStr() incorrectly uses 1, rather than the maximum value, for the count parameter if the count is not specified * dbeRunApp() does not correctly handle running of .CMD files * dbeChr() returns incorrect value if called in a macro * ASCII 'ff' (decimal 256) characters in imported data cause random problems during import and when viewing/using resulting table rows * Length attribute of report fields is ignored when displaying data on reports * Vertically scrolled windows in the query designer sometimes cannot be scrolled back into position after closing and reopening the design * Table window positions in the query designer are not always properly restored after closing and reopening the design * Some very long expressions and conditions in the query designer are truncated after closing and reopening the design * Update queries which involve join operations sometimes update the incorrect rows of the underlying tables * Some update queries which involve a join and an update on the "read only side" of a 1-to-N join would appear to execute rather than display the appropriate error message * Attempting to create a new application when OS/2 Warp FixPak 11 is installed sometimes causes and erroneous error and then application can't be created