|
This release is a new version. This version includes the feature changes and bug fixes listed below. It also introduces two new utilities, nvcheck and nvreorganize.
nvcheck utility is introduced.
The nvcheck utility is a diagnostic tool capable of performing a number of low-level integrity checks on NewViews databases. This version of nvcheck can perform four different checks and additional checks are expected to be included in future releases.
Nvcheck is run from the Windows start menu.
nvreorganize utility is introduced.
The nvreorganize utility is designed to fix problems detected by nvcheck. The only nvreorganize operation in this version performs a complete rebuild of all database indexes. Additional nvreorganize operations are expected to be included in future releases.
Nvreorganize is run from the Windows start menu.
Quickbooks(tm) data conversion available.
We can now export all Quickbooks(tm) data and import it into NV2. Please contact Q.W. Page for more information.
You can now add sub-accounts.
NewViews has "exposed" the (already existing) ability to add sub-accounts by adding a Sub Accounts item to window lists for account (blue) tables.
Although this ability is provided automatically to new windows, for existing windows, i.e. windows created before updating to this release, the Window>Default Setup command must be issued to replace the existing windows. The Sub Accounts item will then appear in their window lists.
Transaction amounts are restricted to two digits right of the decimal place.
Prior to this release, NewViews allowed amounts to have more than two digits to the right of the decimal place. Only two digits are now allowed. This restriction applies only to amount fields, not quantities or rates. This had led to some confusion because the number entered, although it might have more than two fractional digits, was usually formatted with two so the extra digits went unnoticed. You can find such numbers by changing the number format to none, thus displaying all digits.
Text representations of check amounts are now currency neutral.
The formatting of a check amount as text contained the words Dollars and Cents, which were inappropriate for users outside of North America. A future release will allow the user to control the formatting, but until then the format has been changed from this style:
--- Fourteen Thousand Four Hundred Sixty One Dollars And 5 Cents ---
To this:
*** Fourteen Thousand Four Hundred Sixty One 5/100 ***
Print templates can now wrap long fields instead of truncating.
A wrapping capability was added to ITEM_DESCRIPTION on checks, invoices, & statements. Descriptions that are too wide for the cell they are printed in are split into multiple lines. The characters "\n" can be placed in the text to force a line-break to occur where desired.
The total invoice amount is now omitted from all but the last invoice page.
Prior to this release, the total amount for an invoice was printed on every page of a multi-page invoice. Now the total invoice amount is only printed on the last page.
Payroll pay check details are suppressed for zero amounts.
When payroll calculations result in zero amounts on paycheck details, the details are skipped.
Text lines were removed from report name and description indexes.
Each row on a report is usually an account but if the account name is empty it is treated as a simple text line. Text lines are generally used to space out reports or to spread descriptions throughout them for headings. These text lines used to appear on the report when a name or description index was selected but now they appear only when sorted by line number.
Changed "Print Account Ledgers" settings to support open view running balance options.
A new option was added to "Print Account Ledgers" to provide more control over the running balance when printing the open view. The opening running balance of the open view can begin at zero (this was always the case before the change), or it can now start at the closing balance of the closed view.
Note that this functionality has always been available directly on a postings (green) tables using the Postings>View>Closed Balance>Include command, so this change merely upgrades printing options to comply with existing table functionality.
Compressed transactions imported from NV1 are now reconciled.
When importing from NV1 you have the option of compressing transactions. These compressed transactions were not reconciled so they would appear on the open view of account postings (green) tables. To eliminate them from the open views, compressed transactions are now reconciled when imported.
Note, if you have already imported from NV1 and did so using the compression option, you may want to reconcile the compressed transactions to get them out of the way on open views. They are easy to identify and will all appear in one block at the top of the root account postings. Mark them in a block and use Tools>Fill Column to reconcile them all in a single operation.
BUG FIX: Several block operations worked on hidden blocks.
Commands such as Print>Account Ledgers should process a block if a block is marked, or process the active row otherwise. These commands inadvertantly processed a block instead of the active row when a block had been marked but was hidden. This release fixes the problem.
BUG FIX: The Tools>Column Fill command had a problem when used with multi-user access.
Tools>Column Fill had a problem when used on a database with multi-user access. The problem caused some apparently "random" rows to have their fields filled in. The problem only occurred with multi-user access, and only when the column being filled in was itself a component of the table's current index. The most common example occurred when reconciling an account on a postings (green) table where the postings table was sorted in reconcile order. This release fixes the problem.
BUG FIX: Asterisk fill had problems on print templates.
Templates that print amounts, such as on check templates, had glitches in the asterisk fill. This release fixes the problem.
BUG FIX: Accounts payable checks did not display vendor account names.
Prior to this release, ITEM_ACCOUNT on an accounts payable check template did not print the vendor account name, and instead printed nothing. This release fixes the problem.
BUG FIX: Multi-page accounts payable checks generated an inadvertant error.
When there are too many item details on an account payable check, they are continued on the next check stub and that next check is voided. However the error "expected integer but got 1.0" was instead inadvertantly generated in this circumstance. This release fixes the problem.
BUG FIX: Applying payments and deposits now work properly from journals.
The Tools>Apply Payments command now works properly on a bank payment journal, and Tools>Apply Deposits now works properly on a bank deposit journal. Previously, the apply window got "stuck" when attempting to move to the next or previous transaction detail. This release fixes the problem.
BUG FIX: When printing tables, some values were inadvertantly interpreted as dates.
Some values, such as account names containing hyphens, were interpreted by Excel as a date. For example, account name 2-5110 would be displayed in Excel as Feb 10. This release fixes the problem.
BUG FIX: An inadvertant error was generated when printing an account with no postings.
An error was encountered when printing an account's postings if there were no postings in the specified date range. This release fixes the problem.
BUG FIX: A bug occurred in <Post & Print Checks>.
The AP Accounts>Tools>Pay Account command pops up a window to review and pay invoices in full or in part. When the <Post & Print Check> button was pressed an error was inadvertantly generated. This release fixes the problem.
BUG FIX: Error message added when creating sub-journals.
You cannot add a sub-journal to a journal that already has transactions. This error condition was not checked in prior versions.
BUG FIX: Payroll could not recognize non-numeric percent values when importing from NV1.
A payroll import error occurred when a non-numeric value was supplied for a %= payroll code. This release fixes the problem.
BUG FIX: Payroll annual limit is now set correctly when importing from NV1.
A payroll import now correctly sets the annual limit from the %= and r= payroll codes.
BUG FIX: The number of payroll pay periods was slightly incorrect in rare circumstances.
The number of pay periods is used in some payroll calculations. However, the actual number of pay periods in a year can differ from the number that should be used in the calculation. For example, when paying on a bi-weekly basis, the number 26 should be used, but there are actually 27 pay periods in years such as 2005, and 27 was used instead. This release fixes the problem.
BUG FIX: A glitch occurred when importing "boomerang" transactions from NV1.
This is a very obscure problem that only came up in a few circumstances. It only involves data imported from NV1. When a transaction on an NV1 journal consists of two simple items, they are collapsed into a single journal row when imported into NV2. If the two NV1 items representing the transaction post to same account, they are not treated as a "boomerang" by NV1 because they come from separate journal rows. However, after being imported into NV2, the single resulting journal row, posting twice to the same account, is treated as a boomerang. The only difference for a boomerang is that the resulting postings do not appear on account debit/credit views or contribute to account debit/credit histories. The only material consequence of this is that the import reported bogus history amount errors when checking the imported account histories. The importer now detects and compensates for these rare transactions.
BUG FIX: <Control-Click> did not work under some circumstances.
You normally <Control-Click> the left mouse button on a table column title when you want to home in on a target row as you type. However, the <Control-Click> was sometimes ignored if the computer had a keyboard with twelve function keys and the caps-lock happened to be enabled. This release fixes the problem.
BUG FIX: File selection windows would sometimes hang.
The file selection window used for picking templates, running scripts, and so on, would sometimes hang, i.e. never return. This occurred only when the default path used in the selection was on a disk drive or network volume that was no longer accessable. This release fixes the problem.
BUG FIX: Error occurred when changing access objects.
Access objects are connected to the object to which access is being offered, i.e. the target object. The access object's .access_to field is connected to this target object. An error could occur if the name or description of the target object is changed and then the access object is subsequently changed or deleted. This release fixes the problem.
BUG FIX: Audit record was written when evaluation limit was exceeded.
When an attempt to delete an object failed because the evaluation limit was exceeded, an audit record was still inadvertantly created. This release fixes the problem.