Scripts

The Tools>Script Evaluate command is used to run NV2 scripts.

NewViews functionality can be extended through the use of scripts. Scripts are found in the scripts folder: c:/nv/nv2.dat/scripts where c:/nv is assumed to be the NewViews installation folder. When you issue the Tools>Script Evaluate command, you can enter the path to the script, or click <List> to pick from a list of recently used scripts, or click <Browse> to pick a new script from a file explorer.

Here is a review of scripts in the scripts folder:

NV2 Scripts
Name	Runs from	Function
audit_info_columns.qw_script	Can be run from any table.	This script can be run on any table of NewViews objects (e.g. accounts, journal transactions, ledger postings, etc.). Five new columns are appended to the current table to display: Audit Count - a count of the audit items. Audit Date Created - the date the item was created. Audit User Created - the name of the user who created the item. Audit Date Last Change - the date of the last change to the item. Audit User Last Change - the name of the user who last edited the item.
`bank_payment_postings_flip.qw_script`	Run on a table of bank payments headers.	Flips the debit and credit postings, preserving the transaction amount and the reconcile values of the postings.
block_close.qw_script	Any account ledger	Closes (reconciles) a block of itmes on an account
block_close_balance_forward.qw_script	Any account ledger	Closes (reconciles) a block of itmes on an account, also adds a balance forward transaction to each account, setting the closed running balance of he period to zero, and adding an equivalent balance forward open amount for the next period. This script is used in association with Print>Statements which normally prints open-item statements, but when used with this new script, can print balance-forward statements.
database_id_set.qw_script	Anywhere	You can change the database id of an existing database by running this script. You can run the script from anywhere in NewViews. The only requirements are that the database must be in your computer directory space (i.e. not remote through a server), and that the database cannot be open.
`database_template_export.qw_script`	Run on a table of reports.	Export selected reports and everything *above* them in the totaling structure, to an export file. For example, mark the trial balance and the trial balance will be exported, but also exported will be the financial statements above it, such as the balance sheet and income statement, as well as any related summary reports. The bulk of the database. i.e. customers, vendors, products, transactions, audit trail, etc, can be left behind, moving just the basic structure (essentially the chart of accounts and financial reports) into a new set of books using the corresponding database_template_import.qw_script.
`database_template_import.qw_script`	Run anywhere in an application database.	Imports a template file that was exported using the database_template_export script. Generally you would import such a template into a newly created set of books to quickly set up its accounting structure using the original set of books as a starting point.
decompress_transactions.qw_script	mark a block of transactions on the Compressed Transactions Journal.	Can be used if your application database has a Journal Compressed Transactions to decompress summary transactions.
merge_cross_account.qw_script	Can be run from any blue account table of sales or expense accounts.	Merge_Cross_Account is designed to run on a block of sales accounts and provides Mail Merge with the customer information. Merge_Cross_Account can also be run from a block of purchase or expense accounts and gets data from the vendor.
new_column_workstation_port.qw_script	A workstation window	By default, a workstation login is set to port 7890. This script is available to add a field to a login row to specify the port number.
`screen_template_export.qw_script`	Run anywhere in an application database.	Exports the state of all windows to a screen template file. In addition to windows, the screen template includes access information, bookmarks, and pick roots. It represents a comprehensive environment for a user with those access rights on a particular database. The is no corresponding import script. The template is found and imported automatically when a user with a matching access opens a database for the first time from a particular workstation.
server_single_port_to_multi_port.qw_script	A server window	This converts an existing server database from "single-port" to "multi-port". This script will reconfigure the server windows to expose port information that can be modified (e.g. the default port can be changed from 7890 to 7891, etc.)
setup_account_aging_date1.qw_script	Can be run from any blue account table.	Setup_account_aging_date1 provides aging into the future. For example, if a transaction *Order Date* column is retitled *Due Date* and used as an invoice due date, then running the script on a table of accounts will display which invoices are coming due and when.
setup_account_day_of_week_analysis.qw_script	Can be run from any blue account table.	Setup_account_day_of_week_analysis provides a view to see which days of the week transactions are occurring. Simply run the script on any table of accounts and configure the first (i.e. control) column.
sort_items.qw_script	Can be run from any blue account table.	The sort_items script can be used to sort items by any column value. It is typically used when there is no built-in index to select (i.e. when clicking a column title does nothing).
`transaction_all_columns_deep.qw_script`	This script can only be run on the "root" Journal folder. A new window tab is added to explore transaction headers and detail items in the companion window pane. The difference is that the view of headers will show the union of all possible posting columns from all types of transactions.	The detail window pane will respect the type of transaction active in the controlling window pane, and it will switch to the view commonly available for each type of detail items.
`transaction_all_columns_shallow.qw_script`	This script can only be run on the "root" Journal folder. A new window tab is added to explore transaction headers and detail items in the companion window pane. The difference is that the view of both headers and detail items will show the union of all possible posting columns from all types of transactions.	The detail window pane will not respect the type of transaction active in the controlling window pane, and all types of detail items will display using the same column layout as the headers.
`window_template_export.qw_script`	Run anywhere in an application database.	Exports a default setup for each class of window to a separate window template file. There is no corresponding import script. These window templates setups are used automatically whenever new windows are created regardless of workstation, database, or user. Running this script after setting windows up the way you want them enables you to change or override the default setups provided with the NewViews installation.
`workstation_login_screen_delete.qw_script`	Position on a row of a workstation's database login table.	Deletes all windows associated with the user and database identified by the login row. This causes NewViews to find and import a screen template the next time the user opens that database.