When you use the arrow keys to move around in any top pane, the bottom pane displays details about the object you just moved to. This feels sluggish when the bottom pane takes a while to update. Version 2.13.1 corrects this problem because it waits an instant before refreshing the bottom pane. Movement feels more responsive in the top pane.
When you hold an arrow key down to move a long way quickly, the keyboard generates repeating arrow key signals, usually at the rate of about 30 per second. Also, there is a time delay before the repeating signals begin. You can set both the initial time delay, and the time between repeated signals. The initial time delay should be as short as possible, and the signals should repeat as fast as possible. This may make NewViews (and other programs?) feel more responsive.
See Tweak your keyboard repeat delay and rate for more.
Prior to this version, active row highlighting made it difficult to see the ends of a marked block of items, especially if the block only included one or a small number of rows. Version 2.13.1 removes the active row highlighting when the cursor is in a block. This makes it much easier to see the items marked.
Block copy/paste of accounts and transactions is most often used to replicate data, with changes to names and dates, in the same database (i.e. the source and destination database are the same).
Block copy/paste can also be used for NewViews to NewViews inter-database transfer (i.e. the source and destination databases are different, but they must both be NewViews databases). Prior to this version, the clipboard was used as a transfer medium, and it was assumed both the source and destination databases were open. However, there are times when having both databases open and using the clipboard is awkward.
Version 2.13.1 adds the ability to save copy/paste data to a file, which can be transported and read into the destination database at another place and time.
See Block Copy/Paste for more.
Prior to this version, it was only possible to show the account name and description on a Print>Account Ledgers output. In application databases that are sub-foldered, this limitation could cause confusion or error interpreting the output. Version 2.13.1 adds the ability to display the full account path, and the full path of the report the account is on (if any).
See %_path and %_report_path in Printing Account Ledgers for more.
Tools>Import Records has been upgraded to be sub-folder capable. Instead of just accepting account names and report names, full account paths and report paths are also allowed. This means you can create accounts of any type (e.g. AP, AR, BANK, etc.), in a way that respects existing account sub-foldering. You can also create sub-foldered reports, and place new accounts on reports that are sub-foldered. Transactions can post to any account, uniquely, by specifying a full path for the account.
Note that a full journal path can now be specified, but the journal still must be of type GENERAL. A future release, currently under development, will enable the creation of all types of transactions. (Before any programming changes are made by third-party exporters, Q.W. Page should be contacted for advise regarding use of the current Tools>Import Records versus waiting for the new approach under development.)
See Name/Path Formats for more.
A change made in version 2.12.2 caused Print>Account Ledgers to stop printing distribution details. This release fixes the problem.
A change made in version 2.12.2 caused <F9> (goto journal and goto posting) to fail in some circumstances. This release fixes the problem.
Prior to this version, timecard payroll could occasionally have rounding errors, and the books went out of balance by a penny. This release corrects the problem by using more significant digits in the weighted average rate determination. For example, a weighted average rate that displayed 21.25 per hour might now display 21.24895.
Version 2.12.0 introduced better control of Excel from within NewViews (e.g. creation of new workbooks and new worksheets). This requires a complete synchronization with an already running Excel. However, some cases were missed in the testing and user attempts to synchronize with sheets containing complex ranges failed (e.g. links to other sheets). This release should fix the problems.