This release is a service pack only, and no database processing is required. A number of bugs and glitches were fixed. The most important bug fix concerns multi-user collision detection. Although the collision detection algorithm itself was correct, a minor program error caused a bug message to be presented instead of the correct collision error message. A paricularly annoying bug was that if a table cell was being edited at the time you inserted a new row, the cell was cleared.

• More database information in Help About command.

  The Help>About command now displays numbers of objects of various kinds and the size in bytes of the application database.

• No more screen size warnings.

  The warning about low resolution screens now only pops up when you are installing, instead of popping up every time you run NewViews.

• Fixes in database_id_set script.

  The dialog would not dismiss if help had been popped up. Also, the database_id_set script now exits after changing the database id. Users were clicking <OK> after changing the database id and therefore were accidentally changing it yet again.

• msvcp60.dll is now automatically installed on computers that don't have it.

  This is the Microsoft c/c++ version 6.0 runtime package and it should already be on all Windows systems. However, it was omitted from some systems. NewViews now automatically detects the file and installs it if missing. Before this change, some users could not install NewViews without explicitly downloading the runtime package.

• Minor improvements on dialog buttons.

  Better focus management for ok/cancel buttons on basic notify and confirm dialogs.

• Default window setup leaves main explorer tree in "nicer" state.

  This is a strictly cosmetic change. After a default window setup, the main explorer tree leaves itself in a state that makes NV1 (DOS NewViews) users more "at home".

• BUG FIX: Bug occurred when two users were editing the same field.

  When a multi-user collision occurred, instead of reporting the collision error, a bug was reported with message "Attempted to find a master from a null address." and bug number "314120050406093533". The collision error is now reported correctly.

  Credit for finding this bug goes to Albert Sulmistras.

• BUG FIX: Checks were printed with zero amounts when paying vendors.

  Checks with zero amounts were printed when paying vendors. This only occurred when in multi-user access. All amounts in the database were correct but the total amount on the printed check was zero. The check total amount is now printed correctly.

  Credit for finding this bug goes to Albert Sulmistras.

• BUG FIX: Fields were sometimes being incorrectly cleared.

  If you were editing a field and before moving out of the field, i.e. it was still displaying a white background, you issued Edit>Insert or Edit>Insert, the field was cleared. This problem (bug) has been fixed.

• BUG FIX: Fields pasted using Block>Paste were sometimes cleared.

  When you block paste into a table cell, the cell was not switched to edit mode so the cell color did not change to white and unless another field on the same was edited, the pasted information was eventually cleared.

• BUG FIX: Customer information field was missing from window list pull-down.

  When on a customer account and looking the details of a sales invoice, the invoice information windows did not appear in the window list pull-down. This only happened when view the invoice from the books of final entry, i.e. it did not happen when viewing invoices from the journal.