|
Tools>Create Transactions>Post Dated had a bogus error message.
When the prompt settings resulted in no transactions being added, (for example, specified end date less than the current transaction date), a notification window should have been displayed, but instead, an error with a bogus message was displayed. This release fixes the problem.
A bug sometimes occurred when changing summary posting dates.
A bug with message "Encountered unexpected sector." would sometimes occur when several changes were made, during the same session, to the summary posting date setup view of the odds and ends document. This release fixes the problem.
An infinite loop sometimes occurred when changing summary posting dates.
There was a condition under which changing summary postings dates on the odds and ends summary posting dates view could result in an infinite loop occurring. This condition was rare but was encountered at least once. This release fixes the problem.
Reorganizing a summarized database introduced errors.
If a database has been summarized using the summary posting feature introduced in the previous release of version 2.10, (i.e. by specifying summary dates on the summary posting date view of the odds and ends document), then reorganizing the database introduced errors. These errors would typically cause account total amounts to display as zero for the summarized periods. The errors are detected and reported by nvcheck. This release fixes the problem.
If a database has been corrupted by a reorganize, then the database can be fixed by again running nvreorganize on it after installing this release.
Canada Revenue Agency electronic filing transmitter numbers with leading zeros are now allowed, and special characters are handled properly.
A bug occurred converting version 2.09 workstations. Data entry in a ledger quantity column created an error. This release fixes the problem.
It was an error to reconcile timecards that are paid. This release permits paid timecard reconciliation.
In the first release of NV2, reports could have both accounts and sub-reports. A "tighten down the hatches" pass on the code inadvertently removed this ability. This release fixes the problem.