/271820231123152020 {
    .title "Attempted to change a transaction that is on inactive employee XXX."
	.id 271820231123152020
	.tags {error}
    .body {
    	[p {
			You attempted to change or delete a transaction that is on an
            inactive employee.

			An employee is inactive if it's [qw_field_name active] field is set to
            [qw_field_value inactive].
        }]
		[p {
			The following information should help you identify the transaction:
	    }]
        [ul {
            [li [p {
				The transaction is [qw_field_value [qw_s_args .posting_transaction_path]].
            }]]
            [li [p {
				The inactive employee is [qw_field_name [qw_s_args .employee_path]].
            }]]
        }]
    }
}
/271820220805134750 {
	.title "Select Tags value set behavior"
	.id 271820220805134750
	.tags {dialog confirm}
	.body {
		[p {
			The Allocation [qw_field_name "Tags"] value can be a single tag, or a list of many tags.
		}]
		[h3 Replace]
		[p {
			If you choose Replace, the value that is there now will be replaced with the new value.
		}]
		[h3 {Include in List}]
		[p {
			If you choose Include in List, the value that is there now will be modified to include the change, creating a longer list.
		}]
		[h3 {Delete a Pick Root from the List}]
		[p {
			To delete one or more tags from the list, simply edit the value as text and delete the characters for the tag(s) to remove.
            When prompted to Replace or Include in List, choose Replace.
		}]
	}
}
/271820181206145850 {
	.title "General Journal with name \"CDATA\" already exists. Rename it and try again."
	.id 271820181206145850
    .context {Custom Data Install}
	.tags {error}
	.body {
		[p {
			This set of books already has a General Journal with the name [qw_quoted CDATA].
		}]
		[p {
			CDATA is short for [qw_quoted "Custom Data"] and NewViews is appropriating the name for this and future projects.
		}]
		[p {
			Simply rename your original CDATA journal (e.g. CDATA1) and run the install script again.
		}]
	}
}
/271820180130163000 {
	.title "Print Journal Transactions must be run from a table of transaction \"headers\"."
	.id 271820180130163000
    .context {Print Journal Transactions}
	.tags {error}
	.body {
		[p {
			You are positioned in the wrong window for this operation.
		}]
		[p {
			[qw_menu_command Print {Journal Transactions}] will not run on a table of transaction detail items.
		}]
		[p {
            Position on a journal's collection of transaction [qw_quoted headers] and print from there.
		}]
		[p {
			Note that you can also print many journals in one operation by positioning on a table of journals.
		}]
	}
}
/271820170623155630 {
	.title "Custom Data Type Mismatch"
	.id 271820170623155630
    .context {Edit Custom Data Value}
	.tags {error}
	.body {
		[/* {
                ::qw::throw [::sargs \
                    .text "Attempted to edit the value of a custom data field that is not defined for rows of this type." \
                    .help_id 271820170623155630 \
					.definition_class $ClassObject \
                    .object [%_reference odb_master] \
				];

        */ }]
		[/* {
        */ }]
		[
			::set ::DefClass [qw_s_args .definition_class];
			::set ::Object [qw_s_args .object];
			::set ::DefClass [::subst [::string map [::list /OBJECT/NEWVIEWS/SYSTEM ""] [$::DefClass odb_class_path]]];
			::set ::DefClass [::subst [::string map [::list /OBJECT/NEWVIEWS ""] $::DefClass]];
			::set ::Object [::subst [::string map [::list /OBJECT/NEWVIEWS/SYSTEM ""] [$::Object odb_class_path]]];
			::set ::Object [::subst [::string map [::list /OBJECT/NEWVIEWS ""] $::Object]];
			::set ::Html "";
		]
		[p {
			The custom data you are attempting to edit is not defined for items of this type.
		}]
		[p {
			The current item is of type $::Object.
		}]
		[p {
			Data for this column is defined for items of type $::DefClass.
		}]

		[/* {

		[p {
			The current item is of type [::subst $::Object].
		}]
		[p {
			Data for this column is defined for items of type [::subst $::DefClass].
		}]

		[p {
			The current item is of type [::subst [$::Object odb_class_path]].
		}]
		[p {
			Data for this column is defined for items of type [::subst [$::DefClass odb_path]].
		}]

		[p {
			The current item is of type [::subst [[qw_s_args .object] odb_class_path]].
		}]
		[p {
			Data for this column is defined for items of type [::subst [[qw_s_args .definition_class] odb_class_path]].
		}]

		[
			::set ::Text1 "";
			::set ::DefClass [qw_s_args .definition_class];
			::set ::Object [qw_s_args .object];
			::append ::Text1 [$::DefClass odb_path];
			::append ::Text1 [$::Object odb_path];
			::append ::Html [::subst $::Text1];
			::append ::Html "";
		]
        */ }]
	}
}
/907020051012104010 {
	.title "No objects selected for print"
	.id 907020051012104010
	.tags {error}
	.context {W2 Slips, RELEVE1 Slips, T4A Slips, T4 Slips, Statements, 1099 Slips}
	.body {
		[
			::set ::Html "";
			::set ::Error_Line "";
		]
		[p {
			Under these conditions there is nothing to print, and the error is displayed to notify you of this.
		}]
		[h3 {All Items Excluded}]
		[p {
			A possible reason for this error is that you are printing with settings that have excluded all items.
            For example, there may be an option for skipping zero balance accounts and all accounts selected have a zero balance.
		}]
		[p {
			Or, you may have a mismatch between the [bold {Email Status}] setting and the [bold {Email}] address of the account(s) or employee(s).
		}]
		[ul {
			[li {
                [p {
                    When [bold {Email Status}] is set to [bold {active}] only accounts with an email address are selected.
                }]
			}]
			[li {
                [p {
                    When [bold {Email Status}] is set to [bold {inactive}] only accounts with an empty email address are selected.
                }]
			}]
			[li {
                [p {
                    When [bold {Email Status}] is set to empty all accounts are selected (respecting of course any other option values).
                }]
			}]
		}]
		[h3 {Missing Information}]
		[p {
			Finally, the error message may indicate the reason there is no point in proceeding.
            For example, an employee may not need a T4 slip, or a vendor may not have surpassed the limit to receive a T5018, etc.
		}]
		[p {
			Errors/missing information detected when attempting to print/e-file [qw_s_args .slip_type] slips. The errors are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::Error [qw_s_args .errors] {
				::append ::Text1 [li [p "Employee/Vendor: [::lindex $::Error 0]"]]
				::set ::Text2 ""
				::foreach ::Item [::lindex $::Error 1] {
					::append ::Text2 [li [p $::Item]];
				}
				::append ::Text1 [ul $::Text2];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			The missing information must be entered before you can print/e-file these [qw_s_args .slip_type] slips.
		}]
	}
}
/199320170228115300 {
	.title "Errors/missing information detected."
	.id 199320170228115300
    .context {Rent Receipts}
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			Listed below are the accounts with problems.
		}]
		[p {
            Accounts with a rent receipt amount of zero is normal.
            The member/tenant had no activity or reason for a receipt so it is skipped.
            This error is an [qw_quoted FYI] notification.
		}]
		[p {
            If the errors reported include cross accounts that are empty or equal to JOURNAL_BAL then Print Rent Receipts will not work.
            You must create a rent receipt some other way.
		}]
		[p {
			If the errors reported are postings that are not matched or matched more than once then the most likely problem is the prompt settings.
			Check the Bank, Include and Exclude Account Lists - there are omissions and/or overlaps.
			It would be best to correct the prompt settings and then do a [qw_quoted "clean run"] of all rent receipts.
		}]
		[
			::set ::Text1 "";
			::foreach ::Account [qw_s_args .errors] {
				::append ::Text1 [li [div $::Account]];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
	}
}
/199320170810084230 {
	.update {nv2.34.2 (npm)}
	.test_garbage {
	    	::set ::Plural2 [::expr {[::llength [qw_s_args .errors]]==1?{has}:{have}}];
			The following $::Title account$::Plural $::Plural2 errors in the rent data:
    }
	.title "Errors/missing information detected."
	.id 199320170810084230
    .context {Rent Register}
	.tags {error}
	.body {
		[
			::set ::Title [::expr {$::qw_sub_product eq "nph"?{Member/Tenant}:{Resident}}];
	        ::set ::Plural [::expr {[::llength [qw_s_args .errors]]==1?{}:{s}}];
			::set ::Html "";
		]
		[p {
			Errors detected in rent data for the following $::Title account${::Plural}:
		}]
		[
			::set ::Text1 "";
			::foreach ::Error [qw_s_args .errors] {
				::append ::Text1 [li [p "$::Title: [::lindex $::Error 0]"]]
				::append ::Text1 [ul [::lindex $::Error 1]];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
	}
}
/199320170810084231 {
	.title "Errors/missing information detected."
	.id 199320170810084231
    .context {Rent Register}
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			The following member/tenant account(s) have errors in the rent data:
		}]
		[
			::set ::Text1 "";
			::foreach ::Error [qw_s_args .errors] {
				::append ::Text1 [li [p "Member/Tenant: [::lindex $::Error 0]"]]
				::append ::Text1 [ul [::lindex $::Error 1]];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
	}
}
/199320170620285530 {
	.title "Inconsistent province or RGI calculation type."
	.id 199320170620285530
    .context {Populate RGI Utilities}
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			The following Tenants/Members have no RGI items, or the [qw_field_name "RGI Type"] or province do not match
            the [qw_field_name "RGI Type"] and province of the first account processed.
		}]
		[
			::set ::Text1 "";
			::foreach ::Account [qw_s_args .errors] {
				::append ::Text1 [li [p $::Account]];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			When you use the populate utilities tool on a block of accounts,
			all selected accounts should have at least one RGI item,
            the same [qw_field_name "RGI Type"], and be in the same province.
		}]
		[p {
			The first account processed [qw_quoted "sets the stage"] for checking the rest.
		}]
	}
}
/907020051012121600 {
	.title "Errors/missing information detected."
	.id 907020051012121600
    .context {W2 Slips, Releve1 Slips, T4A Slips, T4A Summary, T4 Slips, T4 Summary, T5 Slips, T5 Summary, T5018 Slips, T5018 Summary}
	.tags {error}
	.body {
		[
			::set ::Html "";
			::set ::Error_Line "";
		]
		[p {
			Errors/missing information detected when attempting to print/e-file [qw_s_args .slip_type] slips. The errors are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::Error [qw_s_args .errors] {
				::append ::Text1 [li [p "Employee/Vendor: [::lindex $::Error 0]"]]
				::set ::Text2 ""
				::foreach ::Item [::lindex $::Error 1] {
					::append ::Text2 [li [p $::Item]];
				}
				::append ::Text1 [ul $::Text2];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			The missing information must be entered before you can print/e-file these [qw_s_args .slip_type] slips.
		}]
	}
}
/271820141125170200 {
	.title "Attempted to change a tenant with \"Related To\" tenant(s). Press Help for more."
	.id 271820141125170200
	.tags {error}
	.body {
		[p {
			This error occurs when you are attempting to change the [qw_field_name "Related To"] value of a tenant that has tenants related to him/her.

			The RGI calculation rules require a simple, one-level representation of the [qw_quoted "Family/Benefit"] unit.

			Select a [qw_quoted "Head of Household"] and relate all relevant tenants to this person.

		}]
	}
}

/271820141106121135 {
	.title "Attempted to delete a tenant with \"Related To\" tenants."
	.id 271820141106121135
	.tags {error}
	.body {
		[p {
			This error occurs when you are attempting to delete a [qw_quoted "Head of Household"].
		}]
		[p {
			To delete this tenant, there are two solutions:
		}]
		[ul {
			[li {
                [p {
					First delete all tenants that are [qw_field_name "Related To"] this tenant, and then delete this tenant.
                }]
			}]
			[li {
                [p {
					Or, first change all tenant [qw_field_name "Related To"] values so that no other tenants are related to this tenant, and then delete this tenant.
                }]
			}]
		}]
	}
}

/271820050404141510 {
	.title "Attempted to post to an account that has descendants."
	.id 271820050404141510
	.tags {error}
	.body {
		[/* {
		Maps the following error messages to this help:
        */ }]
		[p {
			This error message occurs when you attempt to post to an account that has accounts [qw_quoted below].
            You cannot post to a [qw_quoted branch] account.
            You can only post to [qw_quoted leaf] accounts.
        }]
		[p {
			If you are not positioned on a branch account and this error occurs, it's because an account is set as a default value for new items.
            You must clear the default value.
        }]
	}
}

/271820050404141440 {
	.title "Attempted to post to an account from a posting that has sub-postings."
	.id 271820050404141440
	.tags {error}
	.body {
		[/* {
		Maps the following error messages to this help:

            "Attempted to post to an account from a posting that has sub-postings."
			"Attempted to set the amount in a posting that has sub-postings."
			"Attempted to set the quantity in a posting that has sub-postings."
        */ }]
		[p {
			This rather obscure error message is generated when the underlying rules
            that govern NewViews transaction work are breached, but it usually indicates a
            straight-forward situation described as follows.
        }]
		[p {
			You have added a ledger item directly to an account and that ledger item
            is serving as the header of a source document, say a sales invoice, vendor invoice
            or other transaction that generally also has line items below.

			The transaction header is already automatically posting to the account you
            added the ledger item to, i.e. the customer or vendor account.

            But you cannot enter amounts or the cross-account in the header.

            Instead, add these to item details below.

            That is, add line-item details (a.k.a. distribution items) to the invoice
            and enter cross-accounts (say sales, expenses, inventory etc) and the
            quantities and amounts there.
        }]
	}
}
/271820120726103030 {
	.title "Select Pick Roots value set behavior"
	.id 271820120726103030
	.tags {dialog confirm}
	.body {
		[p {
			The [qw_field_name "Pick Roots"] value can be a single root, or a list of many roots.
		}]
[/* {
		[p {
			If you choose Replace, the value that is there now ([qw_field_value [qw_s_args .before]]) will be replaced (with [qw_field_value [qw_s_args .value]]).
		}]
		[p {
			If you choose Append to List, the value that is there now ([qw_field_value [qw_s_args .before]]) will have [qw_field_value [qw_s_args .value]] appended to it, creating a longer list.
		}]
*/ }]
		[h3 Replace]
		[p {
			If you choose Replace, the value that is there now
		}]
		[ul {
			[li {[qw_field_value [qw_s_args .before]]}]
		}]
		[p {
            will be replaced with
		}]
		[ul {
			[li {[qw_field_value [qw_s_args .value]]}]
		}]
		[h3 {Append to List}]
		[p {
			If you choose Append to List, the value that is there now
		}]
		[ul {
			[li {[qw_field_value [qw_s_args .before]]}]
		}]
		[p {
            will be replaced with
		}]
		[ul {
			[li {[qw_field_value [qw_s_args .after]]}]
		}]
		[h3 {Delete a Pick Root from the List}]
		[p {
			To delete one or more roots from the list, simply edit the value as text and delete the characters for the root(s) to remove.
		}]
	}
}
/271820111219174400 {
	.title "Open Now or Open Later"
	.id 271820111219174400
	.tags {dialog confirm}
	.body {
		[p {
			The report file has been created, written and closed.
		}]
		[p {
			If you choose to Open Now, your default browser will launch and display the file content for review and/or print.
		}]
		[p {
			If you choose to Open Later, the prompt will dismiss and NewViews is finished with the operation and the file.
            You can open the file at a later time with any browser or HTML file viewer.
		}]
	}
}
/271820110719151133 {
	.title "Transaction edit dates prohibit operation"
	.id 271820110719151133
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			The prompt date range you have specified spills outside your transaction edit date range.
		}]
		[p {
			Your Transaction Edit Begin Date is [qw_s_args .edit_begin_date].
		}]
		[p {
			Your Transaction Edit End Date is [qw_s_args .edit_end_date].
		}]
		[p {
			It is possible that transactions outside your edit date range may be edited by this operation, so it must be prohibited.
            You need to either narrow the date range of the operation, or widen your transaction edit range.
		}]
		[p {
			Typically, you want to set the prompt begin date to the first day after your last tax return (i.e. your last [qw_quoted closed] year).
            And you want to set the end date to a date that includes all purchases (e.g costs for last month's sales are determined by this month's purchases,
            which happens when you invoice sales before you receive purchase invoices).
		}]
	}
}
/271820110717133305 {
	.title "Invalid Amount Type"
	.id 271820110717133305
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			Invalid Amount Type. The valid choices are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::Path [qw_s_args .ok_list] {
				::append ::Text1 [li [p "$::Path"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			You can type a value if you like, but it must be one that appears in the pick list presented when you press [qw_key F3].
		}]
	}
}
/271820110716160328 {
	.title "Invalid Multilple Column Setup Index"
	.id 271820110716160328
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			Invalid Multilple Column Setup Index. The valid choices are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::Path [qw_s_args .ok_list] {
				::append ::Text1 [li [p "$::Path"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			You can type a value if you like, but it must be one that appears in the pick list presented when you press [qw_key F3].
		}]
	}
}
/271820110712115939 {
	.title "Missing Order Ref #"
	.id 271820110712115939
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			Missing Order Ref # detected when attempting to convert orders to invoices. The errors are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::ErrorPath [qw_s_args .error_list] {
				::append ::Text1 [li [p "$::ErrorPath"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			The missing information must be entered before you can convert these orders.
		}]
	}
}
/271820110816183840 {
	.title "Duplicate item postings"
	.id 271820110816183840
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			Two or more transaction detail items are posting to the same account.
			This will confuse the total shipped and backorder quantities displayed on the detail items so it is prohibited.
            The errors are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::ErrorPath [qw_s_args .error_list] {
				::append ::Text1 [li [p "$::ErrorPath"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			Consolidate the multiple items to one and try again.
		}]
	}
}
/271820101208153315 {
	.title "Errors/missing information detected."
	.id 271820101208153315
	.tags {error}
	.body {
		[
			::set ::Html "";
			::set ::Error_Line "";
		]
		[p {
			Errors and/or missing information detected when attempting to print/e-file [qw_s_args .slip_type] slips. The errors are listed below:
		}]
		[
			::set ::Text1 "";
			::foreach ::Error [qw_s_args .errors] {
				::append ::Text1 [li [p "Recipient: [bold [::lindex $::Error 0]]"]]
				::set ::Text2 ""
				::foreach ::Item [::lindex $::Error 1] {
					::append ::Text2 [li [p $::Item]];
				}
				::append ::Text1 [ul $::Text2];
			}
			::append ::Html [ol [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			The missing information must be entered before you can print/e-file these [qw_s_args .slip_type] slips.
		}]
		[p {
			[bold Note]: recipients that don't meet the requirements for a [qw_s_args .slip_type] slip are skipped (e.g. less than the minimum amount).
		}]
	}
}
/271820101124114510 {
	.title "Historic Aging requires Debit, Credit, Open and Closed postings all set to \"yes\"."
	.id 271820101124114510
	.tags {error}
	.body {
		[p {
			All postings must be examined to unravel the past open state of your postings.
            It doesn't matter what is open or closed now.
            Determining what [bold was] open several weeks or months ago is the objective.
		}]
		[p {
			Historically aged debits only or credits only is possible, but it is prohibited.
            The potential for creating incorrect or misleading output
		}]
	}
}
/271820100531110159 {
	.title "Attempted to enter a tag name with illegal characters."
	.id 271820100531110159
	.tags {error}
	.body {
		[p {
			Tag names can only use lower-case letters, digits, underscores and hyphens.
			All other characters are prohibited.
		}]
		[p {
			[qw_quoted "Special characters"] in tag names may eventually cause you problems
            related to data export or database interconnectivity, so it's best not to use them.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 271820100526114343 {[bold "Tag Name Protocols"]}]}]
		}]
	}
}
/271820050404153850 {
	.title "Attempted goto_posting (F9) when no transaction is active."
	.id 271820050404153850
	.tags {error}
	.body {
		[p {
			You must be positioned on a transaction row with data displayed in it.
            A common cause of this error is attempting to [qw_key F9] when positioned in a title row.
		}]
	}
}
/271820050404153830 {
	.title "Attempted goto_posting (F9) with no column active."
	.id 271820050404153830
	.tags {error}
	.body {
		[p {
			To use this command, you must be positioned on a transaction cell which displays information about an account posted to (including the posting amount).
		}]
	}
}
/271820050404152410 {
	.title "User \"[[$User .name] odb_get]\" access to journal \"[::QW::GUI::NEWVIEWS::odb_path_help_format [::sargs .object $Journal .format short_lower_case_folder]]\" is denied."
	.id 271820050404152410
	.tags {error}
	.body {
		[p {
			You do not have access to this journal.
            Contact your system ADMINISTRATOR for assistance.
		}]
	}
}
/271820050404152350 {
	.title "Attempted \"goto_journal [qw_key F9]\" with a window system not configured to support it (xxx)."
	.id 271820050404152350
	.tags {error}
	.body {
		[p {
			goto_journal ([qw_key F9]) has encountered an unexpected error.
            Please contact Q.W. Page technical support and report the 3 digit error number displayed at the end of the error message.
		}]
	}
}
/271820050404152351 {
	.title "Attempted \"goto_posting [qw_key F9]\" with a window system not configured to support it (xxx)."
	.id 271820050404152351
	.tags {error}
	.body {
		[p {
			goto_posting ([qw_key F9]) has encountered an unexpected error.
            Please contact Q.W. Page technical support and report the 3 digit error number displayed at the end of the error message.
		}]
	}
}
/271820050404152340 {
	.title "Attempted goto_journal (F9) when no posting is active."
	.id 271820050404152340
	.tags {error}
	.body {
		[p {
			You must be positioned on a posting row with data displayed in it.
            A common cause of this error is attempting to [qw_key F9] when positioned in a title row.
		}]
	}
}
/271820081117150040 {
	.title "User \"[[$User .name] odb_get]\" access to account \"[[::sargs::get $s_args .after_handle] odb_path_help]\" is denied."
	.id 271820081117150040
	.tags {error}
	.body {
		[p {
			You do not have access to this account.
            Contact your system ADMINISTRATOR for assistance.
		}]
	}
}
/271820050404142400 {
	.title "Attempted \"Go to any account\" with a window system not configured to support it (xxx)."
	.id 271820050404142400
	.tags {error}
	.body {
		[p {
			[qw_menu_command "Go to" "Any Account"] has encountered an unexpected error.
            Please contact Q.W. Page technical support and report the error number displayed at the end of the error message.
		}]
	}
}
/271820081031155200 {
	.title "Attempted \"Print Invoices\" where the print operation is not supported."
	.id 271820081031155200
	.tags {error}
	.body {
		[p {
			Invoices can be printed when positioned on a posting from an invoice header -
            usually on an AR (customer) or AP (vendor) account.
		}]
		[p {
			A common cause of this error is attempting to print an invoice when
            positioned on a posting from an invoice detail item (e.g. on a SALES account).
		}]
	}
}
/271820070925145614 {
	.title "Attempted to create a payroll transaction out of context."
	.id 271820070925145614
	.tags {error}
	.body {
		[p {
			This error occurs when you are attempting to create a new account ledger item.
		}]
		[p {
			One possible reason for this is subtle. For example, if you set a default value in a journal column
            on an account ledger (with [qw_menu_command Edit "Default Value" Set] or [qw_key F12])
            to a payroll journal, the next insert or append will attempt to create a row for a payroll transaction.
            Problem is, this is completely out of context. A payroll transaction can only be created
            in a payroll journal, or within the appropriate payroll folders.
		}]
		[p {
			Clear the journal column default value (with [qw_menu_command Edit "Default Value" Clear])
            or clear default values for all columns (with [qw_menu_command Edit "Default Value" "Clear All"] or [qw_key Ctrl+F12]).
		}]
		[p {
			Another possible reason could be an attempt to block paste transactions that are
            referencing deleted employees or deleted payrolls, or posting
            to deleted accounts. If this is the case, execute a block copy command, select the offending
            buffer entry and delete it. (Adding new payrolls, employees or accounts with the old names will NOT work - in the
            paste buffer, references to objects are stored as database addresses, and since
            database addresses are machine generated, unique and never reused, the addresses of the original objects
            can never be recreated.) Delete the old buffer entry and create a new one if necessary.
		}]
	}
}
/271820070822175624 {
	.title "Valid Print Account Ledger Dates."
	.id 271820070822175624
	.tags {error}
	.body {
		[p {
			Printing account ledger requires three dates that "make sense".
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 150220040805115959 {Printing Account Ledgers}]}]
        }]
	}
}

/271820050404140530 {
	.title "\"$After\" is not a valid setting. Setting must be \"active\" or \"inactive\"."
	.id 271820050404140530
	.tags {error}
	.body {
		[p {

			You are being asked to select an [qw_quoted active] or [qw_quoted inactive] status for the account.

            You entered in the [qw_field_name active] field the invalid value [qw_quoted [qw_s_args .after]].

		}]
    	[p {
        }]
        [ul {
            [li {[link .chm $::qw_manual_file .id 857720050306171028 {More on Account Status}]}]
        }]
	}
}
/271820050404140850 {
	.title "Attempted to create a transaction in a journal that has [[[odb_master] .odb_deriveds] odb_items] sub journals."
	.id 271820050404140850
	.tags {error}
	.body {
		[p {
			Journals in NV2 display all transactions merged together from any journals "below". You cannot enter transactions
            to a journal that has sub journals below. Click on the [bold "+"] of the active folder (if necessary) and examine the
			sub journals below. It is possible this must be done two or more times to eventually find a journal that has
            no sub journals. These "leaf" journals are where transactions are added.
		}]
		[p {
			[bold "NOTE:"] It is also not possible to add sub journals to a journal that already has transactions entered
            into it. The concept is to separate transactions entered directly from transactions merged together from
            sub journals below.
		}]
	}
}
/271820050404140851 {
	.20051223_build_change_1 {}
	.title "Attempted to create a sub payroll of a payroll that has direct payruns, transactions or employees."
	.id 271820050404140851
	.tags {error}
	.body {
		[p {
			"Branch" payroll folders in NV2 can display all payruns, transactions and employees merged together from any
            payroll folders "below". You cannot directly enter payruns, transactions or employees to a payroll that has
            sub payrolls below. Click on the [bold "+"] of the active folder (if necessary) and examine the
			sub payrolls below. It is possible this must be done two or more times to eventually find a payroll that has
            no sub payrolls. These "leaf" payrolls are where payruns, transactions or employees are added.
		}]
		[p {
			[bold "NOTE:"] It is also not possible to add sub payrolls to a payroll that already has payruns, transactions
            or employees added to it. The concept is to separate data entered directly from data merged together from
            sub payrolls below.
		}]
	}
}
/271820050404140852 {
	.20051223_build_change_1 {}
	.title "Attempted to create a sub employee of an employee that has transactions."
	.id 271820050404140852
	.tags {error}
	.body {
		[p {
			"Branch" employee folders in NV2 can display all transactions merged together from any
            employee folders "below". You cannot directly enter transactions to an employee that has
            sub employees below. Click on the [bold "+"] of the active folder (if necessary) and examine the
			sub employees below. It is possible this must be done two or more times to eventually find a payroll that has
            no sub employees. These "leaf" employees are where transactions are added.
		}]
		[p {
			[bold "NOTE:"] It is also not possible to add sub employees to an employee that already has transactions
            added to it. The concept is to separate data entered directly from data merged together from
            sub employees below.
		}]
	}
}
/271820050404140853 {
	.20051223_build_change_1 {}
	.title "Attempted to create a sub payrun of a payrun that has transactions."
	.id 271820050404140853
	.tags {error}
	.body {
		[p {
			"Branch" payrun folders in NV2 can display all transactions merged together from any
            payrun folders "below". You cannot directly enter transactions to a payrun that has
            sub payruns below. Click on the [bold "+"] of the active folder (if necessary) and examine the
			sub payruns below. It is possible this must be done two or more times to eventually find a payroll that has
            no sub payruns. These "leaf" payruns are where transactions are added.
		}]
		[p {
			[bold "NOTE:"] It is also not possible to add sub payruns to a payrun that already has transactions
            added to it. The concept is to separate data entered directly from data merged together from
            sub payruns below.
		}]
	}
}
/271820050404140910 {
	.title "Attempted to create a transaction in a journal that has no tags."
	.id 271820050404140910
	.tags {error}
	.body {
		[p {
			All transactions in NV2 must have one or more [qw_term "tags"]. Tags are used to partition ledgers and
            reports. The most common use of tags is to partition books by transactions of type [bold order], [bold financial],
            or [bold budget].
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 857720050416150706 {Sub Journals and Tags}]}]
        }]
	}
}
/271820050404141550 {
	.title_old "[odb_path_from_master] must be set when [[[odb_outer] .amount] odb_path_from_master] has been set to [[[odb_outer] .amount] qw_get]"
	.title "[odb_path_from_master] must be set when [[[odb_outer] .amount] odb_path_from_master] has been set to [[[odb_outer] .amount] qw_get]"
	.id 271820050404141550
	.tags {error}
	.body {
		[p {
			This error occurs when you are attempting to record an incomplete transaction line item.
            For example, setting an amount to a non-zero value, but not selecting an account to post
            to will create this error.
		}]
		[p {
			[bold NOTE:] You may have to restore (all) windows to see the offending transaction row.
            Either restore the appropriate window or press [qw_key F8] to restore all windows.
            Then examine the transactions to locate the incomplete row (a cell on this row will be highlighted).
		}]
        [p {
            The incomplete transaction is [qw_s_args .transaction_path].
            (A sequence number following a date in this identification is the internal id of a transaction detail item.)
        }]
        [p {
            It is located in the [qw_s_args .journal_path] journal.
        }]
		[p {
			Another possible reason could be an attempt to block paste transactions that are posting
            to deleted accounts. If this is the case, execute a block copy command, select the offending
            buffer entry and delete it. (Adding a new account with the old name will NOT work - in the
            paste buffer, references to accounts to post to are stored as database addresses, and since
            database addresses are machine generated, unique and never reused, the address of the account
            can never be recreated.) Delete the old buffer entry and create a new one if necessary.
		}]
	}
}
/271820050404142440 {
	.title "Attempted to block copy from the table of all accounts."
	.id 271820050404142440
	.tags {error}
	.body {
		[p {
			The [qw_menu_command Block Copy] command for accounts is intended for use on tables
            of accounts of a particular type (e.g. Accounts Payable) or on a report's table of accounts.
		}]
	}
}
/271820050404142441 {
	.title "Attempted to block copy from the table of all payroll accounts."
	.id 271820050404142441
	.tags {error}
	.body {
		[p {
			The [qw_menu_command Block Copy] command for accounts is intended for use on tables
            of accounts of a particular type (e.g. Accounts Payable, or Canada Payroll) or on a report's table of accounts.
		}]
	}
}
/271820050404142510 {
	.title "Attempted to block paste to the table of all accounts."
	.id 271820050404142510
	.tags {error}
	.body {
		[p {
			The [qw_menu_command Block Paste] command for accounts is intended for use on tables
            of accounts of a particular type (e.g. Accounts Payable) or on a report's table of accounts.
		}]
	}
}
/271820050404142511 {
	.title "Attempted to block paste to the table of all payroll accounts."
	.id 271820050404142511
	.tags {error}
	.body {
		[p {
			The [qw_menu_command Block Paste] command for accounts is intended for use on tables
            of accounts of a particular type (e.g. Accounts Payable, or Canada Payroll) or on a report's table of accounts.
		}]
	}
}
/271820050404142620 {
	.title "Attempted to block copy postings from a branch account (i.e. an account folder)."
	.id 271820050404142620
	.tags {error}
	.body {
		[p {
			The [qw_menu_command Block Copy] command for postings is intended for use on a table
            of postings of an individual account.
		}]
	}
}
/271820050404143730 {
	.title "Attempted to copy an item posted from a transaction distribution, Journal \"$JournalName\" date \"$Date\" Ref # \"$RefNumber\"."
	.id 271820050404143730
	.tags {error}
	.body {
		[p {
			The ledger item identified is posted from a transaction distribution item. It is not possible to
            know exactly how to replicate this posting without replicating the entire transaction, header and
            all items. Copying the entire transaction would create many unexpected "side-effect" postings so
            it was decided to make this operation an error.
		}]
		[p {
			As an alternative to an error message, simply skipping the posting was considered (i.e. copy
            only the postings that are not from distribution items). It was decided that copying only some
            of the transactions could cause as much or more confusion as the unexpected side-effects posting scenario.
		}]
		[p {
			A better approach to the copy operation you are trying to perform might be to navigate to the appropriate
            journal and do it there. Or, mark smaller blocks and manually skip the offending postings (at least this
            way you will understand what you are doing).
		}]
	}
}
/271820050404152700 {
	.title "Attempted to create a column that is not the difference between two amount columns."
	.id 271820050404152700
	.tags {error}
	.body {
		[p {
			To create a column that displays the difference between two columns, position on the second
            of two amount columns and issue the [qw_menu_command View Analysis "New Column" Difference] command.
            A new column will be created and it will display the left column minus the active column.
		}]
		[p {
			For example, if you have two amount columns, say A and B, to create a column that displays
            the amount A minus B, position on column B and issue the [qw_menu_command View Analysis "New Column" Difference] command.
            Column C will be created and the number displayed is calculated as follows: [qw_field_value "C=A-B"]
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 150220041129161204 {[bold "Setting Up A Custom Analysis"]}]}]
        }]
	}
}
/271820050404152701 {
	.title "Attempted to create a column that is not the percent change between two amount columns."
	.id 271820050404152701
	.tags {error}
	.body {
		[p {
			To create a column that displays the percent change between two columns, position on the second
            of two amount columns and issue the [qw_menu_command View Analysis "New Column" "Percent Change"] command.
            A new column will be created and it will display the percent change from the left column to the active column.
		}]
		[p {
			For example, if you have two amount columns, say A and B, to create a column that displays
            the percent change from A to B, position on column B and issue the [qw_menu_command View Analysis "New Column" "Percent Change"] command.
			Column C will be created and the number displayed is calculated as follows: [qw_field_value "C=((B-A)/A)*100"]
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 150220041129161204 {[bold "Setting Up A Custom Analysis"]}]}]
        }]
	}
}
/271820050404152702 {
	.title "Attempted to create a column that is not the percent of another amount column."
	.id 271820050404152702
	.tags {error}
	.body {
		[p {
			To create a column that displays one column as a percent of another, position on the second
            of two amount columns and issue the [qw_menu_command View Analysis "New Column" "Percent of"] command.
            A new column will be created and it will display the left column as a percent of the active column.
		}]
		[p {
			For example, if you have two amount columns, say A and B, to create a column that displays
            A as a percent of B, position on column B and issue the [qw_menu_command View Analysis "New Column" "Percent of"] command.
			Column C will be created and the number displayed is calculated as follows: [qw_field_value "C=(A/B)*100"]
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 150220041129161204 {[bold "Setting Up A Custom Analysis"]}]}]
        }]
	}
}
/271820050404153900 {
	.title "Attempted goto_posting when no account is set."
	.id 271820050404153900
	.tags {error}
	.body {
		[p {
			You are positioned in a valid cell to execute this command, but the posting's account reference is empty.
		}]
		[p {
			The goto_posting command [bold "must"] be executed when a cell displaying information from the account posted
            to is active (e.g. the account [qw_field "Name"] or [qw_field "Description"] field, or the [qw_field_name "Amount"]
            posted).
		}]
		[p {
			This is because a transaction can post to two or more accounts. Without activating a field displayed from
            an account, it is not possible to know which account to go to. The most common cause of this error is
            attempting to go to a posting when the [qw_field_name "Date"], [qw_field_name "Ref #"] or [qw_field_name "Comment"]
            field is active.
		}]
		[p {
			[bold "NOTE:"] This command respects your access rights. If you have not been granted access rights to the
            account posted to, an error will occur.
		}]
	}
}
/271820050404153840 {
	.title "Attempted goto_posting on a column that is not a posting."
	.id 271820050404153840
	.tags {error}
	.body {
		[p {
			The goto_posting command [bold "must"] be executed when a cell displaying information from the account posted
            to is active (e.g. the account [qw_field "Name"] or [qw_field "Description"] field, or the [qw_field_name "Amount"]
            posted).
		}]
		[p {
			This is because a transaction can post to two or more accounts. Without activating a field displayed from
            an account, it is not possible to know which account to go to. The most common cause of this error is
            attempting to go to a posting when the [qw_field_name "Date"], [qw_field_name "Ref #"] or [qw_field_name "Comment"]
            field is active.
		}]
		[p {
			[bold "NOTE:"] This command respects your access rights. If you have not been granted access rights to the
            account posted to, an error will occur.
		}]
	}
}
/271820050404153910 {
	.title "Attempted to goto posting from a distribution item when the header account is set."
	.id 271820050404153910
	.tags {error}
	.body {
		[p {
			To go to the posting on the account set in the header of the transaction, activate
            the account cell in the header and issue the command again.
		}]
	}
}
/271820050420161043 {
	.title "Window Setup Completed."
	.id 271820050420161043
	.tags {error}
	.body {
		[p {
			After NewViews exits, you should backup the workstation database to save the window setups.
		}]
		[p {
			In the NewViews installation directory, there is a file for your workstation
            (likely named workstation.nv2 - but it can have whatever name you gave it when you created it).
            In this directory, create a sub-directory named [bold "backup"], if you haven't already
            done so.
		}]
		[p {
            Copy the [bold "workstation.nv2"] file in your [bold "installation"] directory to the [bold "backup"] sub-directory.
		}]
		[p {
			[bold "Backing up your workstation database should be part of your regular backup routine."]
		}]
		[p {
            Though not as critical as your application database(s) (i.e. sets of books), your
            workstation database contains all your window setups and preferences. It can be
            extremely annoying and inconvenient to "lose" a workstation database, because if
            you do lose it (e.g. it is accidentally deleted, or is corrupted) it must be
            recreated and setup all over again.
		}]
	}
}
/907020051106141502 {
	.20050927_build_change_1a {}
	.title "Column titles must be \"description\" or \"name\"."
	.context "Consolidated analysis print settings - choice of report column titles"
	.id 907020051106141502
	.tags {error}
	.body {
		[p {
			You have entered an invalid choice for this setting. The valid choices are:
		}]
		[ul {
			[li {
				[bold [qw_quoted name]] - Use the name of the report for the column title.
			}]
			[li {
				[bold [qw_quoted description]] - Use the description of the report for the column title.
			}]
		}]
		[p {
			You can either type in a valid choice, or press [qw_key F3] to choose from a selection window.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051109094900 {
	.20050927_build_change_1a {}
	.title "Id columns must be a combination of \"name\" and \"description\"."
	.context "Consolidated analysis print settings - choosing the left-most column(s)"
	.id 907020051109094900
	.tags {error}
	.body {
		[p {
			You have entered an invalid choice for this setting. The valid choices are:
		}]
		[ul {
			[li {
				[p {
					name - Print a name column oply
				}]
			}]
			[li {
				[p {
					description - Print a descriptiion column only
				}]
			}]
			[li {
				[p {
					name description - Print a name and description column
				}]
			}]
			[li {
				[p {
					description name - Print a description and name column
				}]
			}]
		}]
		[p {
			Press [qw_key F3] to choose from a selection window.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051107233317 {
	.20050927_build_change_1a {}
	.title "None of the accounts above/below have a balance payable according to the settings specified."
	.context "PRTPAY - User clicks Previous or Next acct, but no accts with O/S balance in that direction"
	.id 907020051107233317
	.tags {error}
	.body {
		[p {
			You have clicked the [bold {Previous Account}] or [bold {Next Account}] button to move up or down to the next
			Accounts Payable account. However, no account above/below the current account has a balance payable according
			to the seetings you have used. Since there is no account with a balance payable to move to in the direction
			you requested, the command cannot be carried out.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 150220040923180706 {More on Paying Vendors}]}]
		}]
	}
}
/907020051108102904 {
	.20050927_build_change_1a {}
	.title "There are no accounts on this report."
	.context "Consolidated analysis print - the report is empty, or there are only text lines"
	.id 907020051108102904
	.tags {error}
	.body {
		[p {
			You have attempted to print a Consolidation Analysis on a report that does not contain any accounts. Since there
			are no accounts, there is nothing to analyse.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051108103312 {
	.20050927_build_change_1a {}
	.title "None of the accounts have a non-zero balance for the range specified."
	.context "Consolidated analysis print - print zero bal accts is no, and all accts are 0.00"
	.id 907020051108103312
	.tags {error}
	.body {
		[p {
			According to the date range and index you have specified, none of the accounts on this report (or in the selected block)
			have a non-zero balance.
		}]
		[p {
			You have also set the [bold {Print Zero Balance Accounts}] to [qw_quoted {no}] so that all accounts
			with a zero balance will be skipped..
		}]
		[p {
			Since there are no accounts with a non-zero balance, and you have chosen to skip zero-balance accounts, there is
			nothing to be printed from this report.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051108121009 {
	.20050927_build_change_1a {}
	.title "The begin date is after the end date."
	.context "Consolidated analysis print settings check"
	.id 907020051108121009
	.tags {error}
	.body {
		[p {
			You have entered a begin date of [qw_s_args .begin_date] and an end date of [qw_s_args .end_date].
		}]
		[p {
			Since the begin date is after the end date, this is an impossible combination of dates.
		}]
		[p {
			Please change either the begin or end date ensuring that the begin date is [bold before] or [bold {equal to}] the end date.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051108121015 {
	.20050927_build_change_1a {}
	.title "The end date has not been specified."
	.context "Consolidated analysis print settings check"
	.id 907020051108121015
	.tags {error}
	.body {
		[p {
			You have entered a begin date but have not entered an end date.
		}]
		[p {
			Please enter an end date (that is on or after the the begin date.)
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051114105200 {
	.20050927_build_change_1a {}
	.title "Invalid choice \"%_value\", choice must be \"ledger\", \"debit\", \"credit\", \"open\", \"open (include closed balance)\", or \"closed\"."
	.context "Consolidated analysis print - invalid index choice"
	.id 907020051114105200
	.tags {error}
	.body {
		[p {
			You have entered an invalid choice for the [bold Index] setting.
		}]
		[p {
			The index settings selects the amounts that are to be included in the amounts.
			The choices are:
		}]
		[ul {
			[li {
				[p {
					Ledger - All transactions
				}]
			}]
			[li {
				[p {
					Debit - Debit transactions only
				}]
			}]
			[li {
				[p {
					Credit - Credit transactions only
				}]
			}]
			[li {
				[p {
					Open - Open (unreconciled) transactions (debit & credit) only
				}]
			}]
			[li {
				[p {
					Closed - Closed (reconciled) transactions (debit & credit) only
				}]
			}]
		}]
		[p {
			Press [qw_key F3] to choose from a selection window.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051114105210 {
	.20050927_build_change_1a {}
	.title "Invalid choice \"%_value\", choice must be \"yes\" or \"no\"."
	.context "Consolidated analysis print - invalid print zero accounts choice"
	.id 907020051114105210
	.tags {error}
	.body {
		[p {
			You have entered an invalid choice for the [bold {Print Zero Accounts}] setting.
		}]
		[p {
			Choose [qw_quoted yes] to include accounts whose balance for the period is 0.00.[br]
			[br]
			Choose [qw_quoted no] to omit these accounts
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051114105220 {
	.20050927_build_change_1a {}
	.title "Invalid choice \"%_value\", choice must be \"yes\" or \"no\"."
	.context "Consolidated analysis print - invalid print zero columns choice"
	.id 907020051114105220
	.tags {error}
	.body {
		[p {
			You have entered an invalid choice for the [bold {Print Zero Columns}] setting.
		}]
		[p {
			Choose [qw_quoted yes] to include report columns where all amounts are 0.00.
			[br]
			Choose [qw_quoted no] to omit these columns.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/907020051114105230 {
	.20050927_build_change_1a {}
	.title "Invalid choice \"%_value\", choice must be either \"budget & actual-budget\", \"budget & budget-actual\", or \"none\"."
	.context "Consolidated analysis print - invalid print budget column choice"
	.id 907020051114105230
	.tags {error}
	.body {
		[p {
			You have entered an invalid choice for the [bold {Print Total Budget & Variance}] setting.
		}]
		[p {
			The valid choices are:
		}]
		[ul {
			[li {
				[p {
					none - No budget and variance columns will be printed
				}]
			}]
			[li {
				[p {
					budget & actual-budget - A budget column is printed, and a variance column where the variance amounts
					are the actual amounts minus the budget amounts.
				}]
			}]
			[li {
				[p {
					budget & budget-actual - As above, but the variance amounts are the budget amounts minus the actual amounts.
				}]
			}]
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020051117124134 {More on Consolidation Analysis Settings}]}]
		}]
	}
}
/271820051117125312 {
	.20050927_build_change_1a {}
	.title "Attempted to delete an account that has [odb_items] price items."
	.context ""
	.id 271820051117125312
	.tags {error}
	.body {
		[p {
			This error was removed...
		}]
	}
}
/271820051115171730 {
	.20050927_build_change_1a {}
	.title "Attempted to edit or delete a \"Detail Compression Transaction\"."
	.context ""
	.id 271820051115171730
	.tags {error}
	.body {
		[p {
			\"Detail Compression Transactions\" are created by NV1 Import to summerize entire
            months of activity. Each contains the details of many transactions that must be
            decompressed to full detail before any changes can be permitted.
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 857720041207155924 {[bold "Decompressing Transactions"]}]}]
        }]
	}
}
/271820051121123042 {
	.20050927_build_change_1a {}
	.title "Default Journals and Accounts."
	.context ""
	.id 271820051121123042
	.tags {error}
	.body {
		[p {
			NewViews creates a handful of journals and accounts that must be present for NewViews to operate properly.
		}]
	}
}
/271820051118144121 {
	.20050927_build_change_1a {}
	.title "Decompress completed."
	.context ""
	.id 271820051118144121
	.tags {error}
	.body {
		[p {
			Transaction decompress should normally complete successfully. In this case simply allow NewViews to shut down and
            remember to backup the database before proceeding.
		}]
		[p {
			If transaction decompress reports that it completed with deleted account warnings, note the following:
		}]
		[p {
			In versions of NewViews prior to 2.06, it was possible to [qw_quoted restructure] books by moving compressed transactions
			from one account to another, and deleting the original source account. Later attempts to decompress will fail to find the deleted
            account. For this reason, restructuring that involves compression transactions is prohibited in version 2.06.
		}]
		[p {
            To recover (i.e. successfully decompress) in cases where versions prior to 2.06 allowed restructuring, version 2.06 decompress will recreate the
            deleted account, with a system generated name (the name of the original, deleted account is in the audit trail, but for
            the decompress code to find it would be difficult, and it may be impossible to recreate the account with the
            original name if the name has been reused).
		}]
		[p {
			The names of the recreated accounts are reported at the end of the status window. Make a list, visit each account and
            decide what to do with the postings (e.g. move them to the same account you moved the compressed transactions to).
			The accounts created are of type GENERAL and they are very easy to find - they will have names like /1133193460_488
            and are almost always found at the top of the GENERAL account list when sorted forward by account name.
		}]
		[p {
            Allow NewViews to shut down and remember to backup the database before proceeding.
		}]
	}
}
/271820051124170956 {
	.20050927_build_change_1a {}
	.title "Decompress Error."
	.context ""
	.id 271820051124170956
	.tags {error}
	.body {
		[p {
			Transaction decompress requires several conditions to be true before it can run.
		}]
        [ul {
            [li {[link .chm $::qw_manual_file .id 857720041207155924 {[bold "Decompressing Transactions"]}]}]
        }]
	}
}
/907020051205111237 {
	.20050927_build_change_1a {}
	.title "No accounts have been selected."
	.context "Print Statements - no block or active row"
	.id 907020051205111237
	.tags {error}
	.body {
		[p {
			You have attempted to print statements from an accounts table but no account row is active, and there
			is no block of accounts marked.
		}]
		[p {
			To print statements you need to either activate (left mouse-click) on an account line, or use the
			[qw_menu_command Block Start] and [qw_menu_command Block End] commands to mark a block of accounts.
			Then issue the [qw_menu_command Print Statements] command again.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 150220040901123610 {[bold "Printing Customer Statements"]}]}]
		}]
	}
}
/271820051207144915 {
	.title "Window Default Setup Required."
	.id 271820051207144915
	.tags {error}
	.body {
		[p {
			New features require a default setup. You can accept and do it now, or cancel and do it later.
            If you cancel, you will be prompted again the next time you activate the item.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 314120050422104251 {[bold "New Features (Version History)"]}]}]
		}]
	}
}
/271820051213100825 {
	.title "Invalid Bank EFT Setting"
	.id 271820051213100825
	.tags {error}
	.body {
		[p {
			This Bank EFT Setting is invalid.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 857720051216115517 {[bold "Bank EFT Settings for Payroll Direct Deposit"]}]}]
		}]
	}
}
/271820051213100830 {
	.title "Invalid Employee EFT Setting"
	.id 271820051213100830
	.tags {error}
	.body {
		[p {
			This Employee EFT Setting is invalid.
		}]
		[ul {
			[li {[link .chm $::qw_manual_file .id 857720051220153258 {[bold "Employee EFT Settings for Payroll Direct Deposit"]}]}]
		}]
	}
}
/907020051208024600 {
	.20050927_build_change_1a {}
	.title "Invalid OCR Date Format"
	.context "PRINT_AP_CHECKS PRINT_CHECKS & PRTPAY - bad or missing check format setting"
	.id 907020051208024600
	.tags {error}
	.body {
		[p {
			You have entered an invalid format. The valid formats are:
		}]
		[
			::set ::Text1 "";
			::foreach ::Choice [qw_s_args .choices] {
				::append ::Text1 [li [p "$::Choice"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			After you have dismissed this help and the error message, press [qw_key F3] to choose a format from a selection window.
		}]
		[p {
			Click here for more information on the [link .chm $::qw_manual_file .id 907020051209115500 .bookmark 907020051213150000 {[bold "OCR Date Format"]}]
		}]
	}
}
/907020051208024610 {
	.20050927_build_change_1a {}
	.title "Invalid Asterisk Amount Format"
	.context "PRINT_AP_CHECKS PRINT_CHECKS & PRTPAY - bad or missing check format setting"
	.id 907020051208024610
	.tags {error}
	.body {
		[p {
			You have entered an invalid format for the asterisk-filled check amount. The valid formats are:
		}]
		[
			::set ::Text1 "";
			::foreach ::Choice [qw_s_args .choices] {
				::append ::Text1 [li [p "$::Choice"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			After you have dismissed this help and the error message, press [qw_key F3] to choose a format from a selection window.
		}]
		[p {
			Click here for more information on the [link .chm $::qw_manual_file .id 907020051209115500 .bookmark 907020051213150010 {[bold "Asterisk Amount Format"]}]
		}]
	}
}
/907020051208024620 {
	.20050927_build_change_1a {}
	.title "Invalid Text Amount Format"
	.context "PRINT_AP_CHECKS PRINT_CHECKS & PRTPAY - bad or missing check format setting"
	.id 907020051208024620
	.tags {error}
	.body {
		[p {
			You have entered an invalid format for the check text amount. The valid formats are:
		}]
		[
			::set ::Text1 "";
			::foreach ::Choice [qw_s_args .choices] {
				::append ::Text1 [li [p "$::Choice"]]
			}
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			After you have dismissed this help and the error message, press [qw_key F3] to choose a format from a selection window.
		}]
		[p {
			Click here for more information on the [link .chm $::qw_manual_file .id 907020051209115500 .bookmark 907020051213150020 {[bold "Text Amount Format"]}]
		}]
	}
}
/907020051208024630 {
	.20050927_build_change_1a {}
	.title "Currency Symbol Not Specified"
	.context "PRINT_AP_CHECKS PRINT_CHECKS & PRTPAY - bad or missing check format setting"
	.id 907020051208024630
	.tags {error}
	.body {
		[p {
			No currency symbol has been entered. The currency symbol is required to properly format either the asterisk-filled check amount, or the text amount (amount of
			the check in words.)
		}]
		[p {
			Please enter the currency symbol that is appropriate for you.
		}]
		[p {
			Click here for more information on the [link .chm $::qw_manual_file .id 907020051209115500 .bookmark 907020051213150030 {[bold "Currency Symbol"]}]
		}]
	}
}
/907020051208024640 {
	.20050927_build_change_1a {}
	.title "Currency Name Not Specified"
	.context "PRINT_AP_CHECKS PRINT_CHECKS & PRTPAY - bad or missing check format setting"
	.id 907020051208024640
	.tags {error}
	.body {
		[p {
			No currency name has been entered. The currency name is required by many of the text amount formats to to properly format the text amount (amount of the check in words.)
		}]
		[p {
			Please enter the name of your currency symbol (eg: dollar, peso, etc.)
		}]
		[p {
			Click here for more information on the [link .chm $::qw_manual_file .id 907020051209115500 .bookmark 907020051213150040 {[bold "Currency Name"]}]
		}]
	}
}
/907020051208024650 {
	.20050927_build_change_1a {}
	.title "Currency Fraction Name Not Specified"
	.context "PRINT_AP_CHECKS PRINT_CHECKS & PRTPAY - bad or missing check format setting"
	.id 907020051208024650
	.tags {error}
	.body {
		[p {
			No currency fraction name has been entered. The currency fraction name the word used for fractions of a currency unit. For example, the fraction name
			for a dollar is "cent". This name is required by many of the text amount formats to to properly format the text amount (amount of the check in words.)
		}]
		[p {
			Please enter the fraction name of your currency.
		}]
		[p {
			Click here for more information on the [link .chm $::qw_manual_file .id 907020051209115500 .bookmark 907020051213150050 {[bold "Currency Fraction Name"]}]
		}]
	}
}
/271820060120125400 {
	.20051223_build_change {}
	.title "Could not complete block paste."
	.id 271820060120125400
	.tags {error}
	.body {
		[p {
			The most likely cause of this error is a change in the database between the time of the block copy
            and the time of the block paste. For example, if you copy a transaction that posts to an account that is later
            deleted, pasting the transaction will cause this error. The account you are posting to at the time of the paste
            can't be found so it is replaced with empty. This will cause an error similar to attempting to record a transaction
            that has an amount but no account specified.
		}]
		[p {
			The paste operation will abort at the point of the error, leaving you positioned on the first item of the
            block pasted. The item after the end of the block is the transaction that could not be completed.
		}]
	}
}
/907020060220164644 {
	.20060207_build_change {}
	.title "Could not create datafile."
	.id 907020060220164644
	.tags {error}
	.args {.tcl_error .filename}
	.body {
		[p {
			The merge datafile could not be created for the reason given below:
		}]
		[
			::set ::Html "";
			::append ::Html [p [qw_s_args .tcl_error]];
			::append ::Html "";
		]
	}
}
/907020060220165145 {
	.20060207_build_change {}
	.title "Merge main document contains merge fields that are not in the data file."
	.id 907020060220165145
	.tags {error}
	.args {error_list field_list}
	.body {
		[p {
			The Main Document [qw_quoted [qw_s_args .main_document]] contains one or more merge field names that are not found in the data file you are merging the document with.
            The names are:
		}]
		[
			::set ::Text1 "";
			::foreach ::Item [qw_s_args .error_list] {
				::append ::Text1 [li [p "$::Item"]]
			}
			::set ::Html "";
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
		[p {
			The following is a list of the names that can be used in merge documents when performing
			a mailmerge from this table:
		}]
		[
			::set ::Text1 "";
			::foreach ::Item [qw_s_args .field_list] {
				::append ::Text1 [li [p "$::Item"]]
			}
			::set ::Html "";
			::append ::Html [ul [::subst $::Text1]];
			::append ::Html "";
		]
	}
}
/271820060411134521 {
	.title "Transaction must balance."
	.id 271820060411134521
	.tags {error}
	.body {
		[p {
			A transaction must balance to zero. Under normal operating conditions this error should not be possible.
            Carefully examine the item you are working on. Correct any errors. If an [qw_menu_command Edit Save] command
            produces the same error, issue an [qw_menu_command Edit Quit] command.
		}]
	}
}
/907020060427112115 {
	.title "Template Range Errors Detected"
	.id 907020060427112115
	.tags {error}
	.body {
		[
			::if {[::llength [qw_s_args .error_list]]==1} {
				::set ::Text "1 error was "
			} else {
				::set ::Text "[::llength [qw_s_args .error_list]] range errors were "
			}
			::append ::Text "detected in the template [qw_s_args .template_filename]. The errors are:"
			::append ::Html [p [::subst $::Text]];
		]
		[
			::set ::Text "";
			::foreach ::Item [qw_s_args .error_list] {
				::append ::Text [li [p "$::Item"]]
			}
			::set ::Html "";
			::append ::Html [ol [::subst $::Text]];
			::append ::Html "";
		]
		[ul {
			[li {[link .chm $::qw_manual_file .id 907020050518142244 {More on document templates}]}]
		}]
	}
}
/907020060427113946 {
	.title "Template Name Errors Detected"
	.id 907020060427113946
	.tags {error}
	.body {
		[
			::if {[::llength [qw_s_args .error_list]]==1} {
				::set ::Text "1 unknown name was "
			} else {
				::set ::Text "[::llength [qw_s_args .error_list]] unknown names were "
			}
			::append ::Text "found in the template [qw_s_args .template_filename]. The names(s) are:"
			::append ::Html [p [::subst $::Text]];
		]
		[
			::set ::Text "";
			::foreach ::Item [qw_s_args .error_list] {
				::append ::Text [li [p "$::Item"]]
			}
			::set ::Html "";
			::append ::Html [ol [::subst $::Text]];
			::append ::Html "";
		]
		[ul {
			[li {[link .chm $::qw_manual_file .id 150220041111172717 {More on template names}]}]
		}]
	}
}
/9070200620090510 {
	.title "Text Amount Does Not Fit In Template Cell"
	.id 9070200620090510
	.tags {error}
	.body {
		[p {
			The amount on check [qw_s_args .check_number] is [qw_s_args .amount]. This amount, when converted to words is:
		}]
		[p {
			[unbreakable_string [sample [qw_s_args .amount_in_words]]]
		}]
		[p {
			This text will not fit in the [b TEXTAMOUNT] cell on the check template you are using. (The cell is
			[qw_s_args .size_available] points in width, but the text requires [qw_s_args .size_required] points.)
		}]
		[p {
			There are several ways to overcome this problem (all require you to open the template file under
			Excel and make adjustments to the [b TXTAMOUNT] cell.):
		}]
		[ul {
			[li {
				[p {
					(Recommended) Set the cell to [qw_quoted {Shrink To Fit}]. To do this, right-click on the cell, choose
					[qw_quoted {Format Cells...}], click the Alignment tab, and then enable [qw_quoted {Shrink To Fit}] by
					clicking in the box.
				}]
				[p {
					This will allow all check text amounts to be auto-sized to fit correctly in the template cell.
				}]
			}]
			[li {
				[p {
					Reduce the font size of the [b TEXTAMOUNT] cell. This will cause the amount in words to print smaller,
					thus allowing more text to fit in the cell.
				}]
				[p {
					The only drawback to this correction is that all amounts will be printed in the smaller font.
				}]
			}]
			[li {
				[p {
					Widen one or more columns to give [b TXTAMOUNT] more room to print.
				}]
				[p {
					This will likely throw off the positioning of other items on the check however, so this is not
					recommended.
				}]
			}]
		}]
	}
}