Version 4.0 Program build history

Version 4.0 Build History

Since its release as 'Build 0' in early April 1998, Version 4.0 of the software has been updated with the following minor enhancements and code fixes.

Build 1 - 26th April 1998:
- Added a menu option to set the margin widths for printed reports, as well as to specify the line width (thickness) for the printing of worksheets (e.g. the lines that divide the columns, etc.).

Build 2 - 27th April 1998:
- Corrected a problem in the Print Options dialog. Previously, if the user chose to print only a range of pages, and then changed his/her mind, the program would continue to insist that 'start' and 'end' page numbers should be input.

Build 3 - 27th July 1998:
- Corrected a problem in the database code which primarily affected very large data files. The symptoms were the generation of error messages such as 'Invalid internal record number' and 'Attempt to read beyond end of file'.
- Added the facility within the report printing code to allow Table (Node) headings to span two pages if necessary, and for entries to be printed over multiple pages (with regard to the latter, the printing logic had previously assumed that an entry would always fit within a maximum of two pages).
- Note that an updated program disk was despatched to all users in early August 1998... no one should still be running a program with a Build Number of less than 3.

Build 4 - 20th August 1998:
- Corrected a program anomaly which prevented the immediate attachment of a 'Note' to the first entry made within a Table (Node).
- Added extensive changes to the 'Output Text File' menu option. These allowed the user to specify the order in which data items were output (previously the order was fixed), and to opt to have multiple actions split according to the persons to whom they were assigned.

Build 5 - 14th September 1998
- Corrected a problem introduced into the program code during Build 4. If the 'List Format' option was chosen when creating a text output file, data fields other than the ones specified would be written to that file.
- Corrected a problem which previously resulted in the incorrect Table (Node) heading data being output to some entries in an Action File. The action text and other relevant details were not affected.

Build 6 - 12th November 1998
- Corrected a problem which previously caused entries to be spuriously moved within the data file. For example, following a certain rather unique sequence of operations in switching between sections of a data file, the first Flow/No entry within a Table (Node) might be moved so as to become the last Flow/No entry in that Table. No data would be lost or changed as a result.

Build 7 - 27th December 1998
- Corrected a problem which related to multiple windows on the same file. If a second window on a file was opened, an editing change made to the data within that window, and it was then immediately closed, the change would not be saved. However, moving to a different entry or input screen before closing the window would have caused the data to be safely written to the file.

Build 8 - 9th January 1999
- Corrected an irritating habit of the program to change all data filenames to uppercase. This was a hangover from Version 3.0 of the program. It had been incorporated to cater for certain tests within Windows NT 3.51 for which uppercase filenames were useful. Following this correction, the creation of a new file as MyDataFile would no longer be automatically (and frustratingly) changed to MYDATAFILE.

Build 9 - 23rd January 1999
- Extended the correction made in Build 8 to back-up files, as well as converted data files created with previous versions of the program. These were also being automatically given uppercase file names.

Build 10 - 24th January 1999
- Corrected a problem which resulted in an error message being generated if a back-up of a data file was taken before any entries had been input. The error message 'Invalid internal record number' was completely benign... it was the software's way of saying that, having successfully completed the back-up, it could not find the first entry in the file. However, it always worrisome to receive error messages, hence the correction.

Build 11 - 5th August 1999
- Corrected a similar problem to that fixed in Build 10. This was the generation of the same error message if an Agenda was printed before any Table (Node) headings were entered into the data file.

Build 12 - 9th August 1999
- Sundry internal code changes and optimisations.

Build 13
- There was no Build 13. You guessed right... superstition triumphed over reason and logic.

Build 14 - 20th August 1999
- Corrected a problem which caused the error message 'Duplicate entry in index' to be generated if all entries in a Table (Node) were transferred individually to another Table using the 'Transfer Entry' menu option. This error message was only generated when running the program under Windows 98 or Windows NT 4.0.

Build 15 - 3rd October 1999
- Extended the functionality of the Causes Database so that it could be used for a study which did not use keywords. This would allow it to be employed, for example, as a means of displaying an extensive and sectionalised checklist during such study meetings.

Build 16 - 10th January 2000
- Added an option to select the method of calculating Risk Factors.
- Added an error trap to prevent the assignment of duplicate multiple action references.
- Extended the scope of the F9 'Repeat previous text' key to enable this operation when paging through a data file (previously it could only be used when adding a new entry).