|
User Data Edit Safety option implemented.
The implementation of this feature always took a back seat to more pressing issues.
Several new confirm and notify prompts were added.
Many commands can significantly alter the database. In cases where you may make a mistake (e.g. Tools>Pay Account to pay all vendors with Confirm/edit Payments set to no), you are prompted to confirm.
Many commands do things that aren't readily apparent on screen (e.g. copy a table column setup or a block copy/paste buffer entry to the clipboard). Commands of this nature will now display a notify prompt.
A new, one-window block copy/paste interface.
Having two separate windows to manage a block copy/paste buffer was awkward (i.e. one window for block copy and another for the block paste preview). These two windows have been amalgamated into one.
Inter-books block copy/paste interface.
Two command buttons have been added to the new one-window block copy/paste interface; a button to copy a buffer entry to the clipboard, and a button to load a buffer entry from the clipboard.
A block copy/paste buffer entry can now be copied to the clipboard and pasted into another NewViews database. This feature can be used to copy report and employee account setups, journal entries, and ledger items from one set of books to another.
Note: Currently, block copy/paste is only supported on account, transaction, and ledger tables. A future version will extend this capability to all tables.
Block paste transactions as-is or with price/cost and trade taxes recalculated.
Prior to this release, a block paste of purchase transactions did not recalculate, but a block paste of sales transactions did! This release introduces user control over the behavior and you will be prompted to select a method.
Tools>Fill Column for transactions as-is or with price/cost and trade taxes recalculated.
Prior to this release, a fill column operation on transactions (i.e. a journal or a ledger), would in many cases recalculate. This release introduces user control over the behavior and you will be prompted to select a method.
Create "private" desktops (to explore data in the same manner as version 2.08 and prior).
Version 2.09 introduced a significant change to the way database explorers function. Prior to version 2.09, each folder had it's own set of windows. It was decided that this approach was overkill, and that one set of windows for all folders of a particular type was good enough. However, some users were upset about the change. In particular, a single set of windows made it impossible to configure the <F3> select key "Pick Root" on a folder by folder basis.
Version 2.09 now includes a qw_script to create a "private" set of windows for any folder. Simply right mouse click on the folder desktop title bar, choose the Tools>Script Evaluate command and run the qw_script found in c:/nv/nv20.exe/object/system/gui/desktop_create.qw_script. This script will create a private set of windows for the active folder, effectively restoring version 2.08 or prior behavior for that folder. Note that this script must be run for each folder for which you wish to have a private set of windows and hence private pick roots.
Fixed a bug that occurred when moving reports to a new folder.
When re-parenting a report, i.e. moving it to a new sub-folder, an index record would be corrupted and this would be detected when nvcheck was run. Running nvreorganize will fix the corruption and this release fixes the problem, so that it will not occur again.
Fixed a bug in folder management.
It was possible to move or attempt to move folders/objects to a destination that would essentially mean the creation of a new "class". For example, moving an account to the root account folder was possible, but this is clearly an error. The only objects currently permitted in the root account folder must be classes, like Accounts Payable or Accounts Receivable. This release fixes the problem.
Fixed a bug in Trial Balance amount display.
The Trial Balance amounts displayed were incorrectly affected by the user's History Display Begin Date. If this date was not early enough to capture all transactions in the database, then the trial balance amounts displayed were not correct. This release fixes the problem.
IMPORTANT NOTE: To effect the fix, you must perform a Window>Default Setup of the Trial Balance Report desktop, followed by a Tools>Create Trial Balance command.
Fixed a bug in the Sales Journals, Tax Information view.
In the tax information view of a sales journal folder, the accounts used for posting tax 1 and tax 2 amounts were not displayed, and it was an error to attempt to select an account. This release fixes the problem.
Fixed a bug that caused Print and Tool prompts to auto-dismiss prematurely.
In a restricted user access situation, some Print and Tool option prompts would prematurely disappear after a single value was edited. This release fixes the problem.
Fixed a bug in Tools>Pay Account auto-incrementing check numbers.
If the Tools>Pay Account command was issued and set off to run by the "Post and Print Check" button, with Confirm/edit Payments set to no, check numbers were not auto-incremented (i.e. every check created and printed had the number of the first check). This release fixes the problem.
Fixed a bug that prevented NV1 books from converting to NV2.
Version 2.09 Service Pack 2 introduced a glitch that prevented NV1 books with payroll from converting to NV2. This release fixes the problem.
Fixed a bug printing option prompt windows.
Print and Tools commands prompt for option values that control the operation of the command. Attempts to print the option window resulted in a bug and/or unpredictable behavior. This release fixes the problem.
Fixed a bug in Print>All prompt options.
Prior to this release, an attempt to edit the print output filename (for a table of accounts) resulted in an erroneous error related to selecting a printer. This release fixes the problem.
Fixed a bug in Print>Account Ledgers, Include Empty Accounts option.
Prior to this release, an account with no activity in the selected range was not properly recognized as an Empty Account. This release fixes the problem.
Fixed a bug in timecard payroll employer contribution allocation.
There was an arithmetic error in timecard payroll employer contribution allocation rates. Employer contributions are allocated using a pie chart constructed from job/expense allocations. If the same job was posted to multiple times in the same pay period, the pie chart was broken. This release fixes the problem.
If you have been running timecard payroll, you may already have misallocated employer contributions. The misallocated contributions may not be material. Inspect the paychecks; you may be content to live with the result. If you want to clean it up, simply unprocess and re-process all payruns created and processed since you installed version 2.09. The only numbers on the paychecks that will change are the employer contribution allocations. Paychecks already printed will not be affected. Feel safe to perform this internal, housekeeping operation.
NOTE: Unprocessing and reprocessing payruns could wreak havoc on a bank reconciliation.
Fixed a bug that prevented a red progress box from disappearing.
There were circumstances under which a progress box with a red title would not disappear after an operation completed. Since no activity is allowed when a red progress box is displayed, the NewViews workstation would appear to hang and would have to be terminated using the task manager. This release fixes the problem.
This problem only occurred when several databases were opened simultaneously on the same server from the same workstation and yet another user initiated the operation on the same server that caused the display of the red progress box.
Fixed a bug that could result in an infinite loop when importing from NV1.
Under rare circumstances, apparently at random, importing from NV1 would sometimes enter an infinite loop. This release fixes the problem.
The Tools>Totalto>Semiloop Search could miss some semiloops.
The management of the totaling structure changed in version 2.09. So-called semiloops were deprecated, meaning that if there are no semiloops in a database then none will be allowed, but if a database already has semiloops then they continue to be allowed. If the semiloop search command can find no semiloops then semiloops are not allowed in the database from that point forward. But a change to the way the totaling structure is managed also introduced a bug into the semiloop search command and sometimes that would result in no semiloops being reported when there were indeed semiloops. Worse, as a result, semiloops could become prohibited in a database that already contained them. In this case, when re-totaling accounts, bogus errors were generated indicating that the re-totaling would introduce a semiloop and that the re-totaling was thus prohibited. This release fixes the problem.
In addition, the Tools>Totalto>Semiloop Search command was previously designed to work only on a local database. This release allows the command to be used on a remote database, i.e. a database opened through a server.
New
features and corrections issued in the initial |