|
This version will convert application databases (i.e. sets of books). Basic performance testing suggests it will take approximately 2 or 3 hours per gigabyte. If you have a time critical schedule (i.e. a payroll to process) allot time for conversion, or perform the time critical tasks in version 2.09 prior to conversion.
Sort account ledgers by order enter
Working on an account's (green) table of postings (ledger items) in order entered is an extremely important feature. You can see a contiguous block of new transactions at the end of the account and it makes it easier to focus on the work at hand. When transactions move around according to a date or reference sort order, users are easily confused or annoyed. Prior to this version, it was not possible to sort by order entered.
Clicking on the line number column title will now sort an account ledger in the order entered.
Remember that a ledger does not have an interactive index. Block>Move>Insert and Block>Move>Append commands are not available.
The ability to explore and report on account ledgers (postings) anywhere and everywhere is a hallmark of NewViews, but it comes at a price. Databases get large and slow as potentially millions of ledger index records build up. Summary postings conquer this problem, squeezing a set of books to a fraction of its original size, without losing any significant detail. Integrity checking and reorganizing databases will take a fraction of the original time, and changing an account totalto will be several, if not several dozens of times faster.
Create transactions is designed to be run from a block of accounts and will automatically create many identical transactions, one per account. This can be used, for example, to charge all members their monthly dues, charge all students for gym uniforms, and so on.
Currently, only transactions of type GENERAL can be created. It is expected the other types (i.e. SALES, PURCHASE, BANK/DEPOSIT and BANK/PAYMENT) will follow.
You can now position on any transaction and issue Tools>Create Transactions>Post Dated to create a series of posted dated copies for the purpose of adding recurring transactions. This is very convenient for recurring expenses, payments, and so on, and also helps to monitor cash flow.
You can now position on any transaction and issue Tools>Create Transactions>Duplicate to create any number of duplicates of the transaction. This is especially convenient for creating a copy of the last transaction without the need for Block>Export and Block>Import.
This new calculator charges interest on the running balance of an account.
Includes Connecticut, Kentucky and Missouri January 01, 2008 tax calculation update.
All United States payroll users in these states will require this version to process payroll after January 1st, 2008.
Includes new T4 Summary Preview and T4 Summary templates.
Includes new T4 summary report.
Canadian payroll, includes new T4 XML Internet File Transfer.
All Canadian payroll users submitting more than 500 slips (T4, T4a, T5s, etc) will require this version to generate T4s after January 1st, 2008.
The order in which employees appear on a paylist is determined by the employee list.
Prior to version 2.09 the employee list sort order was interactive (sorted by Line number). The order in which the employees appeared on the paylist was under the control of the user.
In version 2.09 the employee list sort order was changed to employee_id. It was not possible to control the order in which the employees appeared in the paylist.
With this version the paylist is again based on the interactive order (sorted by Line number) of the employee list. Click on the Line title and move the employees in the order you wish them to appear on the pay list.
When the NewViews version reached 2.10 it became apparent that the name nv20.exe no longer corresponded properly to the current version number and therefore needed to be changed. From version 2.10 onward, the program name will be simply nv2.exe.
You may need to modify the program name in any desktop shortcuts that you have created to run NewViews.
Similarly, the name of the nv20.dat folder has been changed to nv2.dat.
A new test_template_All_common_fields.xls has been added. This test page template will print all common fields for all documents.
All the individual account's address fields have been added. All documents templates can now specify any of the individual fields from an account's address and shipping address.
Three (3) individual demonstration books are now installed with NewViews. Updated Canada and USA demonstration sets of books are provided to help you learn NewViews. New tutorial books are provided to help you learn report arithmetic.
Within each windowpane, the size of the text may be enlarged or reduced by using the
mouse wheel in combination with the control key on the keyboard. Similarly, the text
of this manual may also be increased.
On some computers using the mouse wheel to change the size of the text of the manual
does not work. In this case, you can change the size of the text by clicking on the
Font icon located on the menu bar at the top of this windowpane.
The popup calendar now has buttons to move backward and forward by a month or year so that you don't have to use the keyboard to navigate. Note, you can continue to navigate using <PageUp> and <PageDown> for month movement and <Ctrl+PageUp> and <Ctrl+PageDown> for year movement.
In timecard payroll, employer contribution expenses were unconditionally allocated to shadow the wage allocation, even when the expense account was specified on the payrun settings. This version corrects the problem - i.e. if the contribution expense account is set it will trigger a single posting to that account for the total contribution, and, if the account is left blank it will shadow the wage allocation with many postings.
In Canada payroll, restricted access users could not see ROE detail information (the window was blank).
In payroll, a new payrun could not be created if the table of employees included one or more employees with no Id. After dismissing the error message, NewViews would hang in an error loop. A similar condition could occur if a new employee was added, but no payroll accounts were setup for the employee. With this release, if this condition exists, you can delete the empty employee id line from the table of employees or add the new employees accounts and continue.
In timecard payroll, deleting all timecards for an employee for a pay period and reprocessing the payrun did not update the paylist. This version corrects the problem.