.title "NewViews"
.id NewViews_Help
.tags "manual"
.body {
	dummy
}
/314120050304084225 {
    .title "Attempted to modify reconciled transaction XXX."
	.id 314120050304084225
	.tags "error"
    .body {
		[p {
			Transaction [qw_field_value [qw_s_args .transaction_path]] has been
            reconciled.

			You are not allowed to change or delete a transaction that is reconciled.
	    }]
		[p {
            A transaction is considered to be reconciled if one or more postings
            on the transaction are reconciled.

			If you are attempting to change a transaction header, then the header
            is considered to be reconciled if any posting on the header is reconciled,
            or if any posting on a line item below the header is reconciled.

			If you are attempting to change a line item then the transaction is
            considered to be reconciled if any posting on the line item has
            been reconciled, or if any posting in the header has been reconciled.

            Although you cannot change a line item if the item itself or its header
            has been reconciled, this is independent of other line
            items.

            You can change one line item if others are reconciled.
	    }]
		[p {
            Each posting that is reconciled, and therefore preventing the change,
            is identified below in this help page.
	    }]
		[p {
			Note that reconciled transactions can be changed under several circumstances:
	    }]
        [ul {
            [li {
                [p {
                    You can always change the [qw_field_name reconcile] field
                    on a posting.
                }]
                [p {
					Of course you must be able to reconcile a posting
                    regardless of what other postings on the same transaction
                    are reconciled.

                    You can also clear the [qw_field_name reconcile] to unreconcile
                    the posting.
                }]
            }]
            [li {
                [p {
                    The [qw_field_name "Reconcile Safety"] field on the user
                    options view is set to [qw_field_value "Off"].
                }]
                [p {
                    You can modify reconciled transactions if the current user's reconcile
                    safety is set to off.

                    This is not recommended except in special circumstances.

                    We have to presume that you know what you are doing and we
                    do not want to prohibit functionality arbitrarily.
                }]
            }]
            [li {
                [p {
                    You can unreconcile all postings on a transaction, and then change the transaction.
                }]
                [p {
                    You can unreconcile the postings, make a change, and then
                    set the posting reconcile fields back to what they were.

					Again, this is not recommended except in special circumstances.

                    We have to presume that you know what you are doing and we
                    do not want to prohibit functionality arbitrarily.
                }]
            }]
        }]
		[h3 "Example - A bank deposit for a cash receipt."]
		[p {
			Each line item on a bank deposit for a cash receipt might have the
            amount received from a customer.

			The credit posting on each item posts to the customer.

            The debit posting in the header posts the total received to the bank account.

            The accounts and amounts on the line items can be changed until you
            are satisfied with their accuracy.

			Eventually, however, you will reconcile the deposit on the bank account.

            When the bank posting is reconciled, any attempt to change the
            header of the deposit, or any line items on the deposit, will
            result in an error.
	    }]
	}
}
/314120050304084246 {
    .title "Posting XXX is reconciled with value XXX."
	.id 314120050304084246
	.tags "error"
    .body {
		[p {
			The following information should help you identify a reconciled posting that is
            preventing the modification of the transaction.
	    }]
        [ul {
            [li {
            	[p {
					The reconciled posting is on transaction [qw_field_value [qw_s_args .posting_transaction_path]].
				}]
            	[p {
					This should help you identify the type of transaction containing
                    the posting.
				}]
            }]
            [li {
            	[p {
					The reconciled posting field is [qw_field_name [qw_s_args .posting_field_path]].
				}]
            	[p {
					Each transaction and/or line item can post to more than one account.

					For example, a general transaction will typically have debit and credit
                    posting.

                    Other more complicated transactions types can post to more.

                    For example, a sales invoice can post to a customer account, a sales
                    accounts, and inventory account, a cost of goods sold account, and
                    various tax accounts.

                    The field within the transaction will help you identify the account.
				}]
            }]
            [li {
            	[p {
	                The posting is reconciled with value [qw_field_value [qw_s_args .reconcile_value]].
				}]
            	[p {
                    On an account postings table (green), knowing the reconcile value
                    will help you find and verify the reconciled posting.
				}]
            }]
            [li {
            	[p {
	                The posting posts to account [qw_field_value [qw_s_args .account_path]].
				}]
            	[p {
	                This identifies the account whose postings table (green) contains the reconciled
                    posting.
				}]
            }]
        }]
	}
}
/314120050304094238 {
    .title "Attempted to modify inactive transaction XXX."
	.id 314120050304094238
	.tags "error"
    .body {
		[p {
			Transaction [qw_field_value [qw_s_args .transaction_path]] is inactive.

			You are not allowed to change or delete an inactive transaction.
	    }]
		[p {
            A transaction is considered to be inactive if one or more postings
            on the transaction are inactive.

			A posting is considered to be inactive if it posts to an account that is inactive,
            i.e. the account's [qw_field_name active] field is set to [qw_field_value inactive].

			If you are attempting to change a transaction header, then the header
            is considered to be inactive if any posting on the header is inactive,
            or if any posting on a line item below the header is inactive.

			If you are attempting to change a line item then the transaction is
            considered to be inactive if any posting on the line item is inactive,
            or if any posting in the header is inactive.

            Although you cannot change a line item if the item itself or its header
            is inactive, this is independent of other line items.

            You can change one line item if others are inactive.
	    }]
		[p {
            Each posting that is inactive, and therefore preventing the change,
            is identified below in this help page.
	    }]
	}
}
/314120050304094247 {
    .title "Posting XXX is inactive."
	.id 314120050304094247
	.tags "error"
    .body {
		[p {
			The following information should help you identify an inactive posting that is
            preventing the modification of the transaction.
	    }]
        [ul {
            [li [p {
				The inactive posting is on transaction [qw_field_value [qw_s_args .posting_transaction_path]].
            }]]
            [li [p {
				The inactive posting field is [qw_field_name [qw_s_args .posting_field_path]].
            }]]
            [li [p {
                The posting posts to account [qw_field_value [qw_s_args .account_path]].
            }]]
        }]
	}
}
/314120050304124245 {
    .title "Attempted to change a transaction that is on inactive journal XXX."
	.id 314120050304124245
	.tags {error}
    .body {
    	[p {
			You attempted to change or delete a transaction that is on an
            inactive journal.

			A journal 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 journal is [qw_field_name [qw_s_args .journal_path]].
            }]]
        }]
    }
}
/314120050304145845 {
    .title "Attempted to change/delete a transaction dated outside the user's transaction edit date range option."
	.id 314120050304145845
	.tags {error}
    .body {
    	[p {
			You attempted to add, change or delete a transaction that is dated outside
            the transaction edit date range specified in the options for user
            [qw_field_value [qw_s_args ".username"]].
        }]
        [ul {
            [li [p {
                    The transaction that could not be modified is [qw_field_value [qw_s_args ".transaction_path"]].
				}]
            ]
            [li [p {
                    The date range begins on [quote][qw_field_value [qw_s_args ".edit_begin_date"]][quote].
				}]
            ]
            [li [p {
                    The date range ends on [quote][qw_field_value [qw_s_args ".edit_end_date"]][quote].
				}]
            ]
        }]
    	[p {
			User [qw_field_value [qw_s_args ".username"]] is restricted to the
            date range above unless the user options are changed.
        }]
    	[p {
			Note that an empty date is most often treated by NewViews as an [qw_quoted infinite] date, in the forever future.

			Empty dates are larger than all non-empty dates and that is why the date is question is outside
            your user edit date range.
        }]
    	[p {
			An empty user edit begin date is less than any transaction date
            and an empty edit end date is greater than or equal to any transaction date.
        }]
    }
}
/314120050319164727 {
    .title "Attempted to set a transaction date outside the user's transaction edit date range option."
	.id 314120050319164727
	.tags {error}
    .body {
    	[p {
			You attempted to set a transaction date to a value that is outside
            the transaction edit date range specified in the options for user
            [qw_field_value [qw_s_args ".username"]].
        }]
        [ul {
            [li [p {
                    The transaction that could not be modified is [qw_field_value [qw_s_args ".transaction_path"]].
				}]
            ]
            [li [p {
                    The date range begins on [quote][qw_field_value [qw_s_args ".edit_begin_date"]][quote].
				}]
            ]
            [li [p {
                    The date range ends on [quote][qw_field_value [qw_s_args ".edit_end_date"]][quote].
				}]
            ]
        }]
    	[p {
			User [qw_field_value [qw_s_args ".username"]] is restricted to the
            date range above unless the user options are changed.
        }]
    }
}
/314120050307172851 {
    .title "Attempted to delete an account that has sub-accounts."
	.id 314120050307172851
	.tags {error}
    .body {
    	[p {
			The attempt to delete account [qw_field_value [qw_s_args .path]] failed.

			You cannot delete an account that has derived objects, often
            called [qw_term sub-accounts].

			You have to delete the sub-accounts first.
        }]
    }
}
/314120050307173232 {
    .title "Attempted to delete an account that has accounts totaling to it."
	.id 314120050307173232
	.tags {error}
    .body {
    	[p {
			The attempt to delete account [qw_field_value [qw_s_args .path]] failed.

			You cannot delete a total account that currently has other accounts
            totaling to it.

			If you want to delete the account then you should un-total all
            other accounts that total to it first.
        }]
    }
}
/314120050307173241 {
    .title "Attempted to delete an account that has postings."
	.id 314120050307173241
	.tags {error}
    .body {
    	[p {
			The attempt to delete account [qw_field_value [qw_s_args .path]] failed.

			You cannot delete an account that has postings.

			It likely does not make sense to delete this account.

            If you really need to delete it you must ensure that it has no
            postings first.

            This can only be accomplished by re-posting its transactions to another
            account or by deleting them, and then try again to delete this account.
        }]
    }
}
/314120080208125107 {
    .title "Attempted to delete a summary posting that has postings."
	.id 314120080208125107
	.tags {error}
    .body {
    	[p {
			You attempted to delete what looks like an account ledger item but
            which is instead actually a [qw_term "summary posting"].

            A summary posting represents (i.e. is a summary total of) a number of ledger items (postings) within
            a specified period as controlled by the summary posting date setup view of the
            odds and ends object.

			The summary posting you attempted to delete is a summary of ledger items that
            post to this account and it cannot be deleted as long as those postings
            continue to post to this account.

			The resoning is similar to why you cannot delete an account if
            transactions post to it.
        }]
		[p {
			If you are attempting to delete the summary posting from a ledger view (green),
            then you should be able to click the restore button, opening a window
            below.

            The window below will display the postings that have been summarized by the
            summary posting on which you are positioned in the upper window.
        }]
		[ul {
        	[li {
            	[link .chm $::qw_manual_file .id 271820071208152552 {More on summary postings.}]
            }]
		}]
    }
}
/314120050307183153 {
    .title "Attempted to change the type of an account that has sub-accounts."
	.id 314120050307183153
	.tags {error}
    .body {
		[p {
			Normally you can change an account's parent even if it has sub-accounts,
            but in this case the act of changing the parent is also causing the
            account's [qw_term class] to change.

            Changing the class is not allowed when the account has sub-accounts.
		}]
        [p {
			The re-parenting operation tried to change the account's class
            from [qw_field_value [qw_s_args .class_path_before]]
            to [qw_field_value [qw_s_args .class_path_after]].
        }]
    }
}
/314120050307183159 {
    .title "Attempted to change the type of an account that has accounts totaling to it."
	.id 314120050307183159
	.tags {error}
    .body {
		[p {
			Normally you can change an total account's parent even other accounts total to it,
            but in this case the act of changing the parent is also causing the
            account's [qw_term class] to change.

            Changing the class of an account is not allowed when other accounts total to it.
		}]
        [p {
			The re-parenting operation tried to change the account's class
            from [qw_field_value [qw_s_args .class_path_before]]
            to [qw_field_value [qw_s_args .class_path_after]].
        }]
    }
}
/314120050307183308 {
    .title "Attempted to change the type of an account that has postings."
	.id 314120050307183308
	.tags {error}
    .body {
		[p {
			Normally you can change an account's parent even when it has postings,
            but in this case the act of changing the parent is also causing the
            account's [qw_term class] to change.

            Changing the class of an account is not allowed when it has postings.
		}]
        [p {
			The re-parenting operation tried to change the account's class
            from [qw_field_value [qw_s_args .class_path_before]]
            to [qw_field_value [qw_s_args .class_path_after]].
        }]
    }
}
/314120050307191828 {
    .title "Attempted to create a sub-account of a posting account."
	.id 314120050307191828
	.tags {error}
    .body {
    	[p {
			This account is a posting account and it has postings.

			You cannot create sub-accounts of this account.
        }]
    }
}
/314120050307193109 {
    .title "Attempted to delete an account that has XXX descendants."
	.id 314120050307193109
	.tags {error}
    .body {
    	[p {
			You cannot delete an account that has sub-accounts.

            It is unlikely that you really want to delete this account but if
            you do, you must first delete its sub-accounts.

        }]
    }
}
/314120070130110349 {
    .title "Attempted to create a sub-account of a text line."
	.id 314120070130110349
	.tags {error}
    .body {
    	[p {
			An account without a name is called a text line because it can be used
            for presentation purposes on reports.

            You can use text lines to introduce space between accounts on a report
            when the report is sorted by line number order.

			However, a text line is not an account and therefore you cannot
            use it to create sub-accounts.
        }]
    }
}
/314120070130114918 {
    .title "Attempted to connect a total parent of a total account that has sub-accounts."
	.id 314120070130114918
	.tags {error}
    .body {
    	[p {
			You tried to total account [qw_field_value [qw_s_args .path_help]]
            to another account, but this not allowed because total account [qw_field_value [qw_s_args .path_help]]
            has sub-accounts.
        }]
		[p {
			You can create sub-accounts of a total account but only if it
            is not connected into the account totaling structure; i.e. only if the account
            does not total to anything and nothing else totals to it.

			You can use sub-accounts to organize the total accounts in the account hierarchy,
            but any attempt to connect a [qw_quoted branch] total account (i.e. a total account
            that has sub-accounts) into the account totaling structure would inevitably introduce
            unnecessary and unwanted semiloops in the resulting totaling structure.
        }]
		[ul {
        	[li {[link .chm $::qw_manual_file .id 314120070710132842 {More on semiloops.}]}]
		}]
    }
}
/314120070130120302 {
    .title "Attempted to total to an account that has sub-accounts."
	.id 314120070130120302
	.tags {error}
    .body {
    	[p {
			You tried to total to account [qw_field_value [qw_s_args .parent_path_help]]
            but this not allowed because account [qw_field_value [qw_s_args .parent_path_help]]
            has sub-accounts.
        }]
		[p {
			You can only total to so-called [qw_quoted "leaf"] accounts,
            i.e. accounts that do not have sub-accounts.

			Sub-accounts can be used to organize total accounts in an account hierarchy,
            but connecting to a [qw_quoted "branch"] account (i.e. an account
            that has sub-accounts) would inevitably introduce unnecessary and unwanted
            semiloops in the resulting totaling structure.
        }]
		[ul {
        	[li {[link .chm $::qw_manual_file .id 314120070710132842 {More on semiloops.}]}]
		}]
    }
}
/314120070130112832 {
    .title "Attempted to create a sub-account of a total account that has total kids."
	.id 314120070130112832
	.tags {error}
    .body {
    	[p {
			You tried to create a sub-account of account [qw_field_value [qw_s_args .path_help]]
            but other accounts total to it.
        }]
		[p {
			You can create sub-accounts of a total account but only if it
            is not connected into the account totaling structure; i.e. only if the account
            does not total to anything and nothing else totals to it.

			You can use sub-accounts to organize the total accounts in the account hierarchy,
            but any attempt to connect a [qw_quoted branch] total account (i.e. a total account
            that has sub-accounts) into the account totaling structure would inevitably introduce
            unnecessary and unwanted semiloops in the resulting totaling structure.
        }]
		[ul {
        	[li {[link .chm $::qw_manual_file .id 314120070710132842 {More on semiloops.}]}]
		}]
    }
}
/314120070130112020 {
    .title "Attempted to create a sub-account of a total account that has total parents."
	.id 314120070130112020
	.tags {error}
    .body {
    	[p {
			You tried to create a sub-account of account [qw_field_value [qw_s_args .path_help]]
            but it is a total account and it already totals to other accounts.

            That is, at least one of it's total parent fields has been filled in.

        }]
		[p {
			You can create sub-accounts of a total account but only if it
            is not connected into the account totaling structure; i.e. only if the account
            does not total to anything and nothing else totals to it.

			You can use sub-accounts to organize the total accounts in the account hierarchy,
            but any attempt to connect a [qw_quoted branch] total account (i.e. a total account
            that has sub-accounts) into the account totaling structure would inevitably introduce
            unnecessary and unwanted semiloops in the resulting totaling structure.
        }]
		[ul {
        	[li {[link .chm $::qw_manual_file .id 314120070710132842 {More on semiloops.}]}]
		}]
    }
}
/314120050323113601 {
    .title "Attempted to total to a text line."
	.id 314120050323113601
	.tags {error}
    .body {
    	[p {
			An account without a name is called a text line because it can be used
            for presentation purposes on reports.

            You can use text lines to introduce space between accounts on a report
            when the report is sorted by line number order.

			However, a text line is not an account and therefore you cannot total
            another account to it.
        }]
    }
}
/314120050323113602 {
    .title "Attempted to total from a text line."
	.id 314120050323113602
	.tags {error}
    .body {
    	[p {
			An account without a name is called a text line because it can be used
            for presentation purposes on reports.

            You can use text lines to introduce space between accounts on a report
            when the report is sorted by line number order.

			However, a text line is not an account and therefore you total it to
            another account.
        }]
    }
}
/314120050323113603 {
    .title "Attempted to total to an account that is a class."
	.id 314120050323113603
	.tags {error}
    .body {
    	[p {
        	You cannot total to an account that is an account class object.

            It turns out that using a total parent field to total to an account
            class is unnecessary because an account already automatically totals
            to its class.

            For example, all vendors automatically total to ACCOUNT/AP and therefore
            all vendor postings can be viewed in one place on the ACCOUNT/AP postings
            table.

            There is no need to explicitly total a vandor to ACCOUNT/AP.

            Similarly, all customer postings can already be viewed on the ACCOUNT/AR account,
            inventory postings on ACCOUNT/INVENTORY, and so on.

            In fact, if you have access to the root account. i.e. /OBJECT/NEWVIEWS/ACCOUNT,
            you can view every posting in the database there.

            This is all automatic, without the need manually total accounts using total
            parent fields.
        }]
    }
}
/314120050323113604 {
    .title "Attempted to total to a posting account."
	.id 314120050323113604
	.tags {error}
    .body {
    	[p {
			Accounts can only total to total accounts, not posting
            accounts.

			A total account will have a path like /OBJECT/NEWVIEWS/ACCOUNT/TOTAL/ABC.

            If it does not have /TOTAL in the path then it is not a total account.

            Otherwise it is a posting account.

            You post to postings accounts and the posting accounts in turn total to
            total accounts, which can in turn total to other total accounts.

            But you cannot total to posting accounts.
        }]
    }
}
/314120050323113605 {
    .title "Attempted to total to the same account twice."
	.id 314120050323113605
	.tags {error}
    .body {
    	[p {
			You have attempted to total account [qw_field_value [qw_s_args .kid_path]]
            to the same account, i.e. [qw_field_value [qw_s_args .parent_path]], more than once.

            Check the total parent fields on the account and you will see that one of them
            is already connected to [qw_field_value [qw_s_args .parent_path]].
		}]
        [p {
            There is never any need to total to the same account more than once.

            Although this would be harmless due to the way NewViews manages
            totaling, it would also be confusing.

            For example, when exploring the totaling structure using a tree explorer,
            the same account would appear more than once under the same folder.

            Experience has shown that this is confusing so it is prohibited.
        }]
    }
}
/314120050323113606 {
    .title "Encountered a loop in the totaling structure."
	.id 314120050323113606
	.tags {error}
    .body {
    	[p {
			If you were allowed to total to the account you selected, i.e. [qw_field_value [qw_s_args .parent_path]],
            there would be a [qw_term loop] in the totaling structure.

			[qw_field_value [qw_s_args .kid_path]] would total to other accounts that eventually total
            back to [qw_field_value [qw_s_args .kid_path]], forming the loop.

            If this were allowed, amounts could total forever in an [qw_term "infinite loop"].
		}]
        [p {
            Loops are never necessary or desirable.

            Select another account or leave the total parent field empty.
        }]
    }
}
/314120060504075125 {
    .title "Encountered a loop in the totaling structure."
	.id 314120060504075125
	.tags {error}
    .body {
    	[p {
			You tried to make account [qw_field_value [qw_s_args .kid_path]]
            a sub-account of [qw_field_value [qw_s_args .parent_path]] but
            this would result in a [qw_term loop] in the account totaling structure.
        }]
    	[p {
			[qw_field_value [qw_s_args .kid_path]] would total to other accounts that eventually total
            back to [qw_field_value [qw_s_args .kid_path]], forming the loop.

            If this were allowed, amounts could total forever in an [qw_term "infinite loop"].
		}]
        [p {
            Loops are never necessary or desirable.

            Make this account a sub-account of another account or quit the
            operation.
        }]
    }
}
/314120070713120616 {
    .title "Attempted to create a semiloop in the totaling structure."
	.id 314120070713120616
	.tags {error}
    .body {
    	[p {
			Semiloops are not allowed in the account totaling structure.
        }]
    	[p {
			If you were allowed to total account [qw_field_value [qw_s_args .kid_path]]
            to [qw_field_value [qw_s_args .parent_path]],
            then there would be a [qw_term semiloop] in the resulting account
            totaling structure.

			More specifically it would result in account [qw_field_value [qw_s_args .semiloop_lower_path]] totaling
            more than once to [qw_field_value [qw_s_args .semiloop_upper_path]].
		}]
        [p {
			That does not necessarily mean that [qw_field_value [qw_s_args .kid_path]] would total
            more than once to [qw_field_value [qw_s_args .parent_path]].

            When retotaling [qw_field_value [qw_s_args .kid_path]] it is also possible
            that a semiloop would be introduced that includes accounts somewhere in the sub-tree below
            the account you are retotaling, i.e. [qw_field_value [qw_s_args .kid_path]] in
            this case.
		}]
        [p {
            Semiloops are never necessary or desirable.

            Select another account or leave the total parent field empty.
        }]
		[ul {
        	[li {[link .chm $::qw_manual_file .id 314120070710132842 {More on semiloops.}]}]
		}]
    }
}
/314120050323113607 {
    .title "Could not total XXX to XXX."
	.id 314120050323113607
	.tags {error}
    .body {
    	[p {
			An attempt to total account [qw_field_value [qw_s_args .kid_path]]
            to [qw_field_value [qw_s_args .parent_path]]
            failed for a reason that should be explained in the help below.
        }]
    }
}
/314120050323181101 {
    .title "Attempted to set an account name to \"\" when it has derived accounts."
	.id 314120050323181101
	.tags {error}
    .body {
    	[p {
			An account that has derived accounts, i.e. sub-accounts, must have
            a name.

            You cannot change the name of such an account to empty.

			Allowing an account with an empty name in this situation would
            lead to confusion so it is prohibited.
        }]
    }
}
/314120050323181102 {
    .title "Attempted to set an account name to \"\" when other accounts total to it."
	.id 314120050323181102
	.tags {error}
    .body {
    	[p {
			An account that has other accounts totaling to it must have
            a name.

            You cannot change the name of such an account to empty.

			Allowing an account with an empty name in this situation would
            lead to confusion so it is prohibited.
        }]
    }
}
/314120050323181103 {
    .title "Attempted to set an account name to \"\" when other accounts total to it."
	.id 314120050323181103
	.tags {error}
    .body {
    	[p {
			An account that has postings must have a name.

            You cannot change the name of such an account to empty.

			Allowing an account with an empty name in this situation would
            lead to confusion so it is prohibited.
        }]
    }
}
/314120050323182227 {
    .title "Encountered invalid normal balance XXX."
	.id 314120050323182227
	.tags {error}
    .body {
    	[p {
            The normal balance of an account must be set to [qw_field_value debit] or
            [qw_field_value credit].
        }]
    }
}
/314120050323182345 {
    .title "Encountered invalid normal representation XXX."
	.id 314120050323182345
	.tags {error}
    .body {
    	[p {
            The normal balance of an account must be set to one of the following values:
        }]
		[ul {
			[li {
				[p {
					[qw_field_value perpetual]
    			}]
				[p {
					Use perpetual for accounts that appear
                    on the balance sheet, such as assets, liabilities, and equity
                    accounts.
                }]
            }]
			[li {
				[p {
					[qw_field_value periodic]
    			}]
				[p {
					Use periodic for accounts that appear
					on the income statement, such as revenue and expenses.
                }]
            }]
			[li {
				[p {
					[qw_field_value opening]
    			}]
				[p {
					Use opening for a few special accounts that need to provide traditional
                    opening balances.

                    The primary example of the use of an opening normal representation
                    is retained earnings.

                    A traditional balance sheet will provide separate lines for opening
                    retained earnings, current period to retained earnings,
                    and closing retained earnings.

					The opening retained earnings account will have a opening normal
                    representation.

                    The opening retained earnings will then display the retained earnings
                    balance as at the beginning of the period configured for the balance sheet.

					The current period retained earnings account will have a periodic normal
                    representation.

                    The current period retained earnings will then display the current period retained earnings
                    for the period configured for the balance sheet.

					The closing retained earnings account will have a perpertual normal
                    representation.

                    The closing retained earnings will then display the retainined earnings
                    balance at the end of the period period configured for the balance sheet.
                }]
            }]

        }]
    }
}
/314120050408110129 {
    .title "Attempted to change the class of a transaction that has items below."
	.id 314120050408110129
	.tags {error}
    .body {
    	[p {
			You have attempted to change the class of a transaction by changing
            its journal.

            You cannot do this if the transaction has line item details details below.

        }]
		[p {
			For example, suppose you add a new transaction
            to a vendor's postings (green table). By default it may be added as a general
            transaction on a general journal.

            You can change the journal to another journal, say a purchase invoice journal,
            and the transaction will be automatically converted to a purchase
            invoice.

            But if instead, you first add line item details to the general transaction
            then it can no longer be converted to another transaction type.
        }]
		[p {
			If you have added details to a transaction and you then realize it is a
            transaction of the wrong class, you have two choices.

            Delete the entire transaction and start again, or delete the line item details
            and try again to change the journal.
        }]


    }
}
/314120060504093344 {
    .title "Attempted to create a sub-account of a posting account."
	.id 314120060504093344
	.tags {error}
    .body {
    	[p {
			You tried to make account [qw_field_value [qw_s_args .kid_path]] a
            sub-account of [qw_field_value [qw_s_args .parent_path]].

            This is not allowed because transactions have been
            posted directly to [qw_field_value [qw_s_args .parent_path]].
		}]
        [p {
			Almost all accounts will have postings but that does not mean that
            transactions posted to them directly.

			For example, the postings on a total account are the union of all the postings
            on the accounts that total to it.

            Also, the postings of an account that has sub-accounts are the union of all the postings
            on the sub-accounts.
        }]
		[p {
			You cannot post directly to an account that has sub-accounts, and
            conversely, you cannot add sub-accounts to an account that has
            been directly posted to.
        }]
    }
}
/314120060504093459 {
    .title "Attempted to create a sub-journal of a journal that has transactions."
	.id 314120060504093459
	.tags {error}
    .body {
    	[p {
			You tried to make journal [qw_field_value [qw_s_args .kid_path]] a
            sub-journal of [qw_field_value [qw_s_args .parent_path]].

            This is not allowed because [qw_field_value [qw_s_args .parent_path]]
            is a leaf journal and it has transactions.
		}]
        [p {
			A leaf journal is a journal that has no sub-journals.

            You can only add transactions to a leaf journal.

			Conversely, you cannot add a sub-journal to a leaf journal if it
            already has transactions.
		}]
        [p {


            You cannot add transactions to a journal that has sub-journals,
            i.e. branch journals.

			A sub-journal has transactions but they are the [qw_term union] of all
            transactions on its sub-journals.


			Almost all journals will have transactions postings but that does not mean that
            transactions were added to them directly.

            Specifically, the transactions on a journal that has sub-journals are the union of all the transactions
            on the sub-journals.
        }]
		[p {
			You cannot add transactions directly to a journal that has sub-journals, and
            conversely, you cannot add sub-journals to an journal to which transactions
            have been directly added.
        }]
    	[p {
			You tried to make journal [qw_field_value [qw_s_args .kid_path]] a
            sub-journal of [qw_field_value [qw_s_args .parent_path]] but this
            is not allowed because [qw_field_value [qw_s_args .parent_path]]
            has transactions.

            That is, transactions were directly added to [qw_field_value [qw_s_args .parent_path]].

            Its transactions are not just the [qw_term union] of transactions
            from sub-journals.
		}]
    }
}
/314120060921152534 {
    .title "This change cannot be allowed because journal XXX would have no tags as a result."
	.id 314120060921152534
	.tags {error}
    .body {
		[p {
			Journal [qw_field_value [qw_s_args .journal_path_help]] would have no tags
            as a result of a change you attempted on an ancestor journal.
        }]
		[p {
			A journal must have tags if it has transactions.

			You can change the tags of a journal that has transactions as long as
            it continues to have tags after the change.
        }]



    }
}
/314120060921153734 {
    .title "This change would cause journal XXX to have no tags."
	.id 314120060921153734
	.tags {error}
    .body {
		[p {
			You are connecting journal [qw_field_value [qw_s_args .journal_path_help]] to new
            parent journal [qw_field_value [qw_s_args .parent_journal_path_help]], i.e. making it a sub-journal of [qw_field_value [qw_s_args .parent_journal_path_help]].
        }]
		[p {
			The problem with this is that neither the journal you are changing nor its
            new parent journal has any tags.

            Journal [qw_field_value [qw_s_args .journal_path_help]] has transactions so this cannot be allowed.
        }]
    }
}
/314120060921154225 {
    .title "You cannot make journal XXX a sub-journal of XXX."
	.id 314120060921154225
	.tags {error}
    .body {
		[p {
			You are connecting journal [qw_field_value [qw_s_args .journal_path_help]] to new
            parent journal [qw_field_value [qw_s_args .parent_journal_path_help]], i.e. making it a sub-journal of a [qw_field_value [qw_s_args .parent_journal_path_help]].
        }]
		[p {
			The problem is that as a result, a sub-journal of [qw_field_value [qw_s_args .journal_path_help]]
            will have transactions but no tags.
        }]
    }
}
/314120060921154512 {
    .title "You cannot can make this change to the tags of journal [[odb_master] odb_help]."
	.id 314120060921154512
	.tags {error}
    .body {
		[p {
			You are changing the tags of journal [qw_field_value [qw_s_args .journal_path_help]] to a new
            value.
        }]
		[p {
			The problem is that as a result, a sub-journal of [qw_field_value [qw_s_args .journal_path_help]]
            will have transactions but no tags.
        }]
    }
}
/314120060921163607 {
    .title "This change would result in journal XXX having no tags."
	.id 314120060921163607
	.tags {error}
    .body {
		[p {
			You attempted to change the tags resulting in journal [qw_field_value [qw_s_args .journal_path_help]] having no tags.
        }]
		[p {
			Journal [qw_field_value [qw_s_args .journal_path_help]] has transactions and any
            journal that has transactions must have tags.
        }]
    }
}
/314120080514153101 {
    .title "Transaction work is not allowed when an account is being re-totaled."
	.id 314120080514153101
	.tags {error}
    .body {
		[p {
			You attempted to add, change, or delete a transaction that posts to an
            account that is currently being re-totaled.

			You have changed an account's total parent but you have not committed
            the changes.

			Commit the account by issuing the [qw_menu_command File Save] command
            or else position on the account that is being changed and press [qw_key F5].

            Then try to perform the transaction work again.
        }]
    }
}

/314120080626101641 {
    .title "Are you sure you don't want to start a new statement?"
	.id 314120080626101641
	.tags {dialog confirm}
    .body {
		[p {
			NewViews is guessing that you really want to start a new statement with
            a new prefix instead of simply incrementing the last reconcile value.
        }]
        [p {
			When you use [qw_key F3] to reconcile a ledger item, NewViews takes the
            last reconcile value, auto-increments it, and uses that value.

			Only the last component of a reconcile value is incremented, so if
            the last value was 2006-04-15, then the incremented value would be
            2006-04-16.

			In this example the prefix is 2006-04, corrsponding to the April 2006 bank statement.
        }]
		[p {
			However, to start a new bank statement you must enter the first reconcile
            value in it's entirety.

            For example, when you reconcile the first item of the May 2006 bank
            statement, you must enter 2006-05-1.

            You can then proceed by clicking [qw_key F3] and each subsequent reconcile value
            will be 2006-05-2, 2006-05-3, and so on.

            The prefix is good for the rest of the items on this statement.
        }]
		[p {
			NewViews cannot automatically start reconciling a new statement for you because
            it simply does not know that a new statement is being started.

            However, NewViews can detect that the last item was not reconciled
            today, and because an entire bank statement is usually reconciled in
            one data-entry session, it is likely that you really intended to start a new
            statement.

			If you are simply resuming a reconcilation operation that you began on a different
            day, then just reconcile the item anyway.

            It is more likely, however that you are starting a new statement, and in
            that case click [qw_button Cancel] and type in the entire
            reconcile value such as 2004-05-1.
        }]

        [ul {
            [li {
            	[link .chm $::qw_manual_file .id 150220041004123906 .bookmark 314120080626122247 {More on auto-incrementing reconcile values.}]
            }]
        }]
        [ul {
            [li {
            	[link .chm $::qw_manual_file .id 150220041004123906 {More on bank reconciliation.}]
            }]
        }]
	}
}
/314120080627104817 {
    .title "Reconcile edit assist is only defined for BANK and GENERAL accounts."
	.id 314120080627104817
	.tags {dialog confirm}
    .body {
		[p {
        	The edit assist key, i.e. [qw_key F3], can only be used on the reconcile field
            of BANK and GENERAL accounts, and not on accounts of other classes.

			You used edit assist on an account of class [qw_field_value [qw_s_args .class_path]].
        }]
		[p {
			The purpose of the edit assist key, i.e. [qw_key F3], on a reconcile field is
            to generate auto-incrementing reconcile values.

            This speeds up the reconciliation process and helps to ensure that reconciled items are sorted
            in a meaningful and useful way.

			However, reconciliation is only performed on BANK accounts, and for
            maximum flexibility, also GENERAL accounts.
        }]
        [ul {
            [li {
            	[link .chm $::qw_manual_file .id 150220041004123906 .bookmark 314120080626122247 {More on auto-incrementing reconcile values.}]
            }]
        }]
        [ul {
            [li {
            	[link .chm $::qw_manual_file .id 150220041004123906 {More on bank reconciliation.}]
            }]
        }]
	}
}
/314120080627104818 {
    .title "Reconcile edit assist is only defined for open items."
	.id 314120080627104818
	.tags {dialog confirm}
    .body {
		[p {
        	The edit assist key, i.e. [qw_key F3], can only be used on open items.

			You are currently positioned on an account ledger that contains
            closed items or could contain closed items.

            Instead, you must switch to an open view of the account.
        }]
		[p {
			The purpose of the edit assist key, i.e. [qw_key F3] on the reconcile
            field is to close an open item by filling in the reconcile field.

            It only makes sense that the items must open, i.e. unreconciled,
            and therefore you must be positioned
            on an open view of the ledger.

			Note that you can also reconcile items by manually entering a reconcile value,
            but the edit assist key enters auto-incrementing reconcile values.

            This speeds up the reconciliation process and helps to ensure that reconciled items are sorted
            in a meaningful and useful way.
        }]
        [ul {
            [li {
            	[link .chm $::qw_manual_file .id 150220041004123906 .bookmark 314120080626122247 {More on auto-incrementing reconcile values.}]
            }]
        }]
        [ul {
            [li {
            	[link .chm $::qw_manual_file .id 150220041004123906 {More on bank reconciliation.}]
            }]
        }]
	}
}