LazLiteDB Files

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Release 2024-04-16

Bug:
For single table projects or master-detail projects, changing the SQL statement mode) caused the columns to revert to default size... fixed 
Work around possible: No

Minor Bug:
For master-detail projects, selecting a different record in Master table sets the column widths to default in Detail tables... fixed=no, solution not found. Partial solution: the detail columns now auto-size to the minimum size required by the cell contents.
Work around possible: No

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Release 2024-04-10

Minor Bug:
For master-detail projects, changes to column width of detail table were not recorded... fixed 
Work around possible: Yes (manually edit width settings in INI file.)
 
Bug:
Using LazLiteDBadmin to copy an encrypted database, the password dialog did not appear... fixed
Work around possible: Yes (Use an alternative database editor.)

Minor Bug:
If an editable column is the first column, the custom editor does not appear until you select another field and then return to the column... fixed
Work around possible: yes   (actually the first column should always be a non-editable RecID Integer AutoInc field. In that case, the issue would not occur.)

There are other minor changes to improve the user experience.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Release 2024-04-05

Minor Bug:
There was a maximum visible width set for a grid. The limit has been removed so it possible to use the width using multiple screens... fixed
Work around possible: No

Minor Bug:
Scroll bars not always visible... fixed
Work around possible: No

Minor Bug:
When configuring a table in LazLiteDB_admin, an error terminating the configuration process with other changes being lost... fixed.
Work around possible: Yes

Bug:
When configuring a table in LazLiteDB_admin, simply changing the order of fields is not recognized as a change so the new order is not saved... fixed
Work around possible: Yes  Make minor additional change and then save. Then undo the minor change

Minor Bug:
Project file names were stored in the INI files with absolute paths included. This caused issues when the installation location was changed (on a portable USB stick for instance). Now only the filename is stored. This will affect any previous projects you have created... fixed
If you have created any projects the fix:
   Edit the project INI files (Notepad) and remove the path from the file names or recreate the project.
   It does not affect any data content in your databases.
Work around possible: Yes

Minor Bug:
If fields were added to an existing table, the INI file did not update to reflect the new fields. This was only a problem with respect to the column title feature that allowed the titles to be rotated... fixed
Work around possible: Yes (manually edit INI file)

Minor Bug:
If fields were deleted from an existing table, the INI file did not update column title entries to reflect the deleted fields. This does not cause any issue other than having data stored for missing columns... fixed = not yet
Work around possible: Yes (manually edit INI file)

Minor Bug:
When setting up field drop-down values in LazLiteDB_admin, clicking on the field type rather than the field name failed to edit the drop down values... fixed.
Work around possible: Yes

Minor Bug:
Memory leak in LazLiteDB_admin... fixed.
Work around possible: No

Bug:
If a field that uses drop-down data selection is the first field, the drop-down does not appear until you select another field and then return to the field with the drop-down option... fixed = not yet
Work around possible: yes   (actually the first field should always be a RecID Integer AutoInc field. In that case, the issue would not occur.)

Changes:
When importing a database via CSV source, all fields now default to CHAR rather than TEXT. This makes SQL changes immediately available in LazLiteDB. You should still adjust the field types to more closely reflect the table data. 

An installation script is included that will install "Start" CMD files that are independent of the disk letter of the installation directory. This is useful when using a portable device for installation where the drive letter sometimes changes. The other alternative would be to force a consistent drive letter for the device such as drive "Z". In that case, the shortcuts installed at the time of installation would work correctly.

There are other minor changes to improve the user experience.