Current Version is 2.25.5  Click Here to Download

The most recent release is all you need to update from any prior release.
You do not need to update to each release between the one you currently have and the most recent one
(i.e. it's okay to "leapfrog" all the way to the current release).

NewViews 2.25

Released - December 20, 2012

This is a version change, not just a service pack. The service pack number is reset to zero. After installing this version, each workstation, server, or application database will be automatically processed the first time you open it. You will be asked for confirmation before any processing is performed, and as a precaution, a backup is made automatically before each conversion.

What's New

• Payroll 2013 update
  • Includes Canadian January 1, 2013 tax calculation update.
    
    All Canadian payroll users will require this version to process payroll after January 1st, 2013.
    
    
  • Includes United States January 1, 2013 tax calculation update.
    
    Political turmoil relating to taxes and a "just-in-time" delivery attitude on the part of legislators and bureaucrats makes providing timely payroll releases a challenge.
    
    As of December 20, 2012 Publication 15 (Circular E), Employer's Tax Guide, Publication 926 and Notice 1036 for 2013 are not available. There are no changes to the 2012 withholdings with this release.
    
    All United States payroll users will require this version to process payroll after January 1st, 2013.
    
• Updated Interface
  
  The user interface has been further simplified.
  
  Access/Audit window tabs were present on every window pane, resulting in unnecessary clutter for a function most people never use. Version 2.25 removes all of these window tabs and replaces them with a "global" Audit menu command. A "top level" access and audit explorer window will pop up when this command is issued, for the purpose of auditing the active object (e.g. the active table row, or in the active detail window). It is more robust since it can be launched at any time, and it saves you the effort and potential confusion of re-navigating to the same object in the correct Access/Audit window tab.
  
  Also, redundant Column Define [F11] windows were removed (a private define window for every table was overkill). A single Column Define window, for every login, is sufficient. Together with removing Access/Audit window tabs, workstation databases are now smaller and a little bit faster.
  
  Several minor cosmetic changes were made to "clean up" and simplify the interface.
  
  
• Database Utilities Repair Transaction Amounts Command
  
  It has been concluded that most index record integrity problems occur in transaction header amounts. This command, added to the Database Utilities dialog, will check just transaction amounts. For extra speed you can also restrict the command to a date range, to transaction headers only (no details checked), and to posting accounts only (no total accounts checked). Experience shows that with such restrictions most problems are still detected. In addition, the command repairs any problems found on the spot so that a reorganize is not necessary.
  
  
• Database Utilities Reorganize Transactions Command
  
  This command, added to the Database Utilities dialog, will rebuild all index records associated with a selected date range of transactrions. This reduces the need to reorganize an entire database when the problem is known to lie with specific transactions. Note that the repair transaction amounts above is more often used for a quick check, and does makes no changes unless problems are found, whereas transaction reoganize always performs a full index rebuild for the selected transactions.
  
  
• Database Utilities Repair Floating Addresses Command
  
  You are unlikely to need this command unless directed by customer support. We mention it here for completeness.
  
  
• Transaction Proof Check Upgraded
  
  The transaction proof check command checks selected transactions against specified proof accounts and detects transactions that would cause a proof account to go out of balance. The command did not detect all occurences of this situation but has been upgraded to find them all. In addition, the diagnostic information reported has been enhanced.
  
  
• Help>TeamViewer Support menu command
  
  TeamViewer is an incredibly useful tool for resolving customer support issues. It allows a Q.W. Page customer support specialist to see you screen and solve your problem quickly.
  
  However, some users found it difficult or tedious to start the TeamViewer program using Microsoft's start menu, so this version includes a simple NewViews menu command to do it (Help>TeamViewer Support).
  
  
• Mail Merge templates can now include Notes
  
  Printing the Notes of an account is now possible.
  
  There is no command in NewViews to directly print the Notes of an object (e.g. account, report, journal, etc.). This means there is no command to print the notes of many objects at the same time in a batch (i.e. the generic Print>Detail Windows command). Until there is a direct notes printing capability, you can use the upgraded Tools>Mail Merge, which now offers NOTES in Microsoft Word's Insert Merge Field list.
  
  
• Print Account Ledger Open View
  
  A common question, not easily answered until this version, is "how do I print an open ledger view, with an opening balance coming from the end of the closed view?"
  
  Viewing this information on screen has long been simple enough. For example, shown below is a ledger open view, with the menu positioned to show the opening balance choices. Notice also the three amount columns in the blue table of accounts. They are configured to show the actual balance, closed balance and open balance, respectively.
  
  However, getting a simple printed version of this information was difficult. Print>Account Ledgers>Simple doesn't support open and closed printing, and the date range control found in Print>Account Ledgers>Advanced can be confusing, and tedious to configure.
  
  A Print>Account Ledgers>Advanced options window is shown below. Notice the three dates that control the opening balance and the range of items printed (option rows 7, 8, 9) are blank. This, together with the selection of Open Postings and an Opening Balance Type of all_closed, will print an open view with the opening balance and running balance as expected.
  
  
• Print AP Checks can now display detail cross accounts
  
  Print>AP Checks now supports ITEM_CROSSACCOUNT. If the invoices being paid are simple transactions, this new field will display the cross account name.
  
  It has come up that the item detail of each invoice being paid could be printed. This is currently not possible, but there have been requests for this feature. It might waste a lot of pre-printed check forms, but in some circumstances it may make sense. If you consider check-run previews, or requisitions for permission to pay invoices, it makes a lot of sense. A future version will address these features.
  
  
• Payroll Paylist supports menu command Tools>Fill Column
  
  This often requested feature is in this release. The Tools>Fill Column command also functions on T4 Lists (for box 52) and W2 Lists (for box 12DD and box 12W).
  
  
• Canada Payroll 53 period ROE templated printing
  
  Pay periods 28-53 can now appear on an ROE print template. (Note: this information has always been available in the Box 15 Earnings Details window tab - now you can put these values on the ROE template)
  
  Also, the old rule that if all pay period values have a non-zero value, then print none has been replaced by the new rule of always print.
  
  
• USA Payroll Fringe Benefits
  
  Employees now have a Benefits window tab. Up to four non-cash fringe benefits can be managed.
  
  
• USA Payroll Vacation Pay Summary
  
  A Vacation Pay Summary is an at-a-glance synopsis of the vacation pay standing of all employees.
  
  
• USA Payroll User Edit W2 Boxes 12DD and 12W
  
  Some users requested the ability to edit the W2 List amounts for box 12DD and box 12W, including support for Tools>Fill Column to set a value for many employees with one command.
  
  This version includes this capability, but you should not "mix methods". Meaning, you either track these amounts on a per-pay-period basis, or edit the zero amount to some value at year end.

<Back to Top>

Problem / Bug Fixes

• Record amounts bugs largely eliminated.
  
  NewViews would sometimes display a bug message with text like "encountered unexpected changes to record amounts" or "Could not find a record with key XXX". A cause of this problem has been found and eliminated and hopefully it was the only cause. In previous versions this type of bug could only be corrected by a database reorganize, and this is a time-consuming operation on very large databases. Now the problem, if detected in the future, will be corrected dynamically and quietly, and you will not even realize such a problem was detected and corrected. Presumably such problems, if detected, were introduced in versions prior to this release.
  
  
• File pick browse button went into infinite loop.
  
  When you pressed a file pick list window's browse button and the current file was on a drive that didn't exist, NewViews would go into an infinite loop and the file browse window would never come up.
  
  
• Pay accounts had a bug after database export/import.
  
  After using database export and import, the system could crash when positioning on the pay accounts settings. This problem was corrected.
  
  
• When using Edit>Cut and Edit>Paste commands to move items from one folder to another, with the destination table sorted by interactive, the position of the paste operation did not respect the current position of the cursor. The moved items were simply appended and appeared at the end of the table, requiring a manual block move to put the items in the intended position.
  
  The paste operation now respects the current cursor position as the destination location.
  
  
• Transaction windows have detail window tabs that display the ledgers of the accounts posted to. The titles of these ledger windows did not show the Sort: and Tag: information.
  
  
• When positioned on a table of accounts, with the current active cell in an amount column, the detail windows respect the settings of the active cell. For example, if the account cell date range is set for a month, the detail ledger window will display only postings for that month.
  
  In the case where the detail window is positioned in the History tab, the history display did not respect the tag of the controlling account table cell.
  
  
• In some cases, when positioned on a TOTAL account row in a table of accounts, the edit assist [F3] key caused an error.
  
  
• Quebec Releve1 box .a now includes box .m in its sum.
  
  
• Quebec Releve1 - added box V, W and box O codes O-CA, O-CB, O-CC, O-RX
  
  
• Several miscellaneous fixes and tweaks.

<Back to Top>

NewViews 2.25 Service Pack 1

Released - January 10, 2013

What's New

• January 2013 Payroll - USA
  
  Includes United States January 01, 2013 tax calculation update.
  
  All United States payroll users will require this version to process payroll after January 1st, 2013.
  
  Political turmoil relating to taxes and a "just-in-time" delivery attitude on the part of legislators and bureaucrats makes providing timely payroll releases a challenge.
  
  As of January 9, 2013 Publication 15 (Circular E), Employer's Tax Guide is not available. This provisional 2013 USA payroll is based on Notice 1036. FICA, Social Security rate for the employee set at 6.2%
  
  
• Bolded Column Title for Sorted By
  
  It's now easier to notice the sort order of a table of items.
  
  The sortby column title already included a cheveron (i.e. v for forward and ^ for reverse), and the window title always displayed the sort order (there are cases where the sortby column is not displayed).
  
  Bolding the sortby column title makes this important piece of information pop off the screen. The appearance and behavior of NewViews can be strikingly different from one sort order to the next. This will help you to keep the sort order in mind.
  
  
• You can now send an email with a PDF attachment for the following tax reporting slips: T4, T4A, T5, T5018, RELEVE1, W2 and 1099.
  
  
• Several Database Utilities operations such as database reorganize and record integrity check run "noticeably" faster on large databases. For example, checking one example database now takes about 9 hours instead of 14 hours. Results may vary.

<Back to Top>

Problem / Bug Fixes

• The database utilities Reorganize>Transactions command had errors.
  
  The database utilities Reorganize>Transactions command was introduced in the last release (2.25.0) and it had a bug that could currupt records. The corruption of these records was not detected by any database utilities check operations. However, a bug would be reported if you attempted to change any of the transactions that were in the date range processed by a Recorganize>Transactions command, due to the curruption of these records.
  
  This release fixes the problems from recurring but it does not automatically fix the corrupted records if you previously ran the database utilities Reorganize>Transactions command. First note that no data has been lost. Second note that it you attempt to change any of the corrupted transactions they are fixed dynamically and you will likely not even notice the fix happening. Third, you can fix the transactions explicitly by performing a database reorganize, or by again issuing the (now fixed) database utilities Reorganize>Transactions command on any date range that includes the transactions that were processed using version 2.25.0.
  
  
• Multiuser server/workstation could freeze during long-duration operations.
  
  This problem only occurred when a workstation had more than one database open on the same server and performed a long-duration operation. Both the server and the workstation could freeze if the operation was "long enough".
  
  
• Distribution item running balance was not displayed properly when in multiuser.
  
  When accessing a remote database (i.e. multiuser) and working on any distribution items (invoices, payments, etc.), the running balance was updated properly but did not display properly when entering and editing detail line items. This problem was introduced in the previous release (2.25.0) and only occurred when operating with multiuser access.
  
  
• Some window database (i.e. workstation) conversions to version 2.25 failed.
  
  Some window databases would not convert due to corruption in prior versions. This corruption is now detected and fixed during the conversion operation.
  
  Although the cause of the corruption was also found and fixed, a new repair operation was added to database utilities. The database utilities command is Repair>Dangling Window Objects;
  
  
• Problem in database utilities reorganize database and recorganize account history.
  
  When using database utilities to rebuild account histories or reorganize a whole database, an error was reported if the operation encountered an account ledger reconcile field whose contents began with a hyphen ("-") character. This problem was rare and only recently encountered. It has been fixed in this release.
  
  
• Version 2.25.0 added the ability to Print>Account Ledgers>Advanced with no date ranges specified. However, a typo caused a bug and the case where a date range is specified printed no items, when items should have printed.
  
  It has been fixed in this release.
  
  
• Version 2.25.0 added the ability to Tools>Fill Column on a payroll Paylist table. However, a bug was introduced which appeared in some cases of other uses of the command.
  
  It has been fixed in this release.

<Back to Top>

NewViews 2.25 Service Pack 2

Released - January 17, 2013

What's New

• Payroll 2013 update
  • Includes United States January 1, 2013 tax calculation update.
    
    All United States payroll users will require this version to process payroll after January 1st, 2013.
    
    This release includes the updated Notice 1036 (Rev. January 2013) new Percentage Method Tables for Income Tax Withholding with 7 brackets.
    
    As of January 17, 2013 Publication 15 (Circular E), Employer's Tax Guide is not available.
    

Problem / Bug Fixes

• Database reorganize reported a "bogus" error.
  
  The Database Utilities Reorganize>Database command reported an error at the very end. This error actually occurred when attempting to update the status line with the message "Reorganize succeeded.". So the reorganize actually completed successfully and the error could be ignored. This release fixes the problem.

<Back to Top>

NewViews 2.25 - Service Pack 3

Released - January 31, 2013

What's New

• January 2013 Payroll - USA updated Missouri and Oregon State withholding tables
  
  
• Improved Control of Amount Column Title Display
  
  Prior to this release, amount column titles (on blue account tables) displayed the column definition options in a pre-formatted manner, or you could enter any text in the Title field of the column definition. Many users didn't want printouts with all the column definition information in each amount column title, but entering new text every time the definition changes is tedious.
  
  This release permits the substitution of data from the column definition into text you enter. For example, now a balance sheet amount column could be titled "Year Ended: %_end" and when the column defined period End Date changes, the new date will be substituted in place of "%_end".
  
  
• Help About added to Database Utilities
  
  Help>About was added to database utilities.

Problem / Bug Fixes

• Server may have been running "slowly".
  
  The server was inadvertantly writing diagnostic information to the standard output. This caused the server to slow down when it was run without redirecting standard output, which is the case when running from the Windows Start menu (as opposed to running from the command line with redirection specified). This release fixes the problem.
  
  
• Amounts in account tables (blue) may not have appeared to update.
  
  Suppose you were editing an account on a blue table of accounts. Suppose further that the NRep field (normal representation) is set to Yes in the column header and you change the normal representation of the account you are editing. Changing the normal representation should alter the date range for the amount and it should normally change immediately. However, although the "underlying" database values were correct in this situation, the displayed amount would not change immediately. Note that if you moved off the document and came back it would be displayed correctly. This release fixes the problem.
  
  
• Remote database backup had a folder creation problem.
  
  When performing a backup of a remote database, a check for the existance of the backup folder was inadvertantly performed on the workstation computer instead of the server. This could sometimes cause confusing error messages informing the user that a folder did not exist or could not be created when it seemed obvious that it should not be a problem (on the server). This release fixes the problem.
  
  
• An obscure error could occur when changing a transaction's journal.
  
  Under very specific circumstances the following error message could occur:
  
  "can't read "Newborn": no such variable"
  
  The circumstances are as follows. You added a transaction to a ledger (green) and set it's journal to a sales or invoice journal, for example. The transaction expects line item details (a.k.a. distribution items). The header already posts to the account (say customer or vendor) but you got an appropriate error when you entered the cross-account in the header, which is not allowed. Then you changed the journal to another journal such as GJ, and the error shown above pops up. This release fixes the problem.
  
  
• A user set the Options value for the Root User for Automatic Pick Boxes to empty. There was a bug, when combined with this situation, that prohibited further editing of any data. This release fixes the problem.
  
  As a note, the Root User options for values that are yes/no or on/off should not be set empty. It's better to set them explicitly.
  
  
• New ROE's (Records of Employment - Canadian Payroll) were creating displaying a "machine representation" of the ROE Issue Code. This release fixes the problem.
  
  
• There are cases in USA Payroll - for the states of California and Illinois - where two types of State Excemptions Claimed are required. The way to achieve this is to enter the number of exemptions, for example, as 1.2 for one exemption of the first type and two of the second type.
  
  
• There was a bug in the view of Accounts named Invoice Aging - Due Date. (This view is optionally installed for a table of accounts by executing the command Tools>Script Evaluate and selecting the script setup_account_aging_date1).
  
  In many cases the amounts displayed for the total coming due in each future period were incorrect. This release fixes the problem.

<Back to Top>

NewViews 2.25 - Service Pack 4

Released - March 19, 2013

Problem / Bug Fixes

• THIS IS A CRITICAL UPDATE THAT MUST BE INSTALLED IMMEDIATELY BY ALL USERS RUNNING NEWVIEWS VERSION 2.25.3
  
  This release corrects a mistake in the data recovery system of version 2.25.3 that prevented your data from being recovered properly after a system crash. If you experienced a system crash with version 2.25.3 you can still restore your books from a backup but you will lose data that has been entered since your last backup. Alternatively, you could run nvcheck and perform the check operations numbered 1 through 4. If any of these four checks report errors contact Q.W. Page Technical Support for assistance.
  
  Although system crashes are uncommon, installing Service Pack 4 will ensure that the NV2 data recovery capability is functioning properly.
  
  
• There were long pauses when pasting blocks of accounts into reports.
  
  Long pauses occurred when pasting accounts into very large reports or equivalently into any blue tables of accounts. This occurred only on very large tables and only when the table was in line number order. This release eliminates these pauses.
  
  
• Problem with Database Utilities Reorganize>Transactions command.
  
  The Database Utilities Reorganize>Transactions command is supposed to process a date range of transactions, rebuilding their indexes and account histories. So one of the purposes of the Reorganize Transactions utility was to fix account history errors (detected using the account history check utility) without the need for a full database reorganize. However, the problem was that although the indexes were rebuilt, the account histories were not processed and therefore the utility did not fix problems with the account histories. This release fixes the problem.
  
  
• The Database Utilities Account History check was reporting inadvertant errors.
  
  The Database Utilities Account History check was in some circumstances reporting errors that did not exist. Although this was related to the existance of transactions with empty dates, that is not longer an issue and this release fixes the problem.

<Back to Top>

NewViews 2.25 - Service Pack 5

Released - May 10, 2013

Problem / Bug Fixes

• THIS IS A CRITICAL UPDATE THAT MUST BE INSTALLED IMMEDIATELY BY ALL USERS RUNNING NEWVIEWS VERSION 2.25.3 or 2.25.4
  
  This release corrects a mistake in the data recovery system of version 2.25.3 and 2.25.4 that prevented your data from being recovered properly after a system crash. The previous release 2.25.4 provided a similar fix but did not fix the problem in all circumstances and this release completes the fix. If you experienced a system crash with version 2.25.3 or 2.25.4 you can still restore your books from a backup but you will lose data that has been entered since your last backup. Alternatively, you could run nvcheck (i.e. Start NewViews Database Utilities) and perform the check operations numbered 1 through 4.
  If any of these four checks report errors contact Q.W. Page Technical Support for assistance.
  
  Although system crashes are uncommon, installing service pack 2.25.5 will ensure that the NV2 data recovery capability is functioning properly.

<Back to Top>