/271820150107134010 {
	.title "Range specifications require a list of key name and value pairs."
	.id 271820150107134010
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[p {
			The value of range begin and end specifications must be an even numbered list of key name and value pairs.
			For example, a valid specification might look like:
		}]
		[ul {
			[li {Range Begin [qw_field_value ".name a"]}]
			[li {Range End   [qw_field_value ".name a"]}]
		}]
		[p {
			This example specification would display only items that have a name beginning with the character [qw_quoted a].
            In the case of a single table cell summing information from [italic below], only items beginning with the character [qw_quoted a] would be summed.
			Notice that all key names begin with the dot character.
		}]
		[p {
			The key component(s) of index [qw_field_value [qw_s_args .object_path][qw_s_args .index_path]] are [qw_field_value [qw_s_args .key_names]]
		}]
	}
}

/271820140513142115 {
	.title "Attempted to delete a column which \"controls\" other columns."
	.id 271820140513142115
	.tags {error}
	.body {
		[p {
			This error occurs when you attempt to delete a column that other columns rely on for configuration information,
            typically an end date, or a begin and end date, or a tag, etc.
		}]
		[p {
			Deleting this column would effectively disable other columns so it is prohibited.
		}]
	}
}

/271820140126132020 {
	.title "Attempted to private setup a window that is already private or is nested within a private setup."
	.id 271820140126132020
	.tags {error}
	.body {
		[p {
			This error occurs when you attempt to issue the command [qw_menu_command Window "Private Setup"] on a window that is already private,
            or is nested within a private setup.
		}]
		[p {
			Setting a window private when it is already private clearly makes no sense.
            The [qw_quoted "nested within"] case occurs when you already have a private setup [qw_quoted above] the folder you are trying to private setup.
            For example, if you private setup folder /ACCOUNT/AR/INTERNATIONAL attempting to private setup folder /ACCOUNT/AR/INTERNATIONAL/USA will cause this error.
		}]
		[p {
			It was decided to limit the number of private window setups to [qw_quoted "one per path"] and not allow a private setup nested within another.
            In practice it seemed to offer too many opportunities for confusion.
		}]
		[p {
			To undo a private setup simply right mouse click on the title bar of the private setup window and execute the menu command [qw_menu_command Window "Default Setup"].
			This will delete the private setup windows and revert to the default setup windows.
		}]
	}
}

/271820140126132010 {
	.title "Attempted to private setup an \"inner\" detail window."
	.id 271820140126132010
	.tags {error}
	.body {
		[p {
			This error occurs when you attempt to issue the command [qw_menu_command Window "Private Setup"] on a window that is not intended for private setup.
		}]
		[p {
			The most common case occurs with [qw_quoted inner] detail window panes.
            You have to back out to the outermost title bar that identifies a window for an object of a NewViews class:
            ACCOUNT (any type), JOURNAL (any type), and REPORT.
		}]
		[p {
			Note that there is one exception to the outermost title bar rule.
			If you are a restricted access user with a table of access points (as opposed to a full tree explorer)
            and you have access to a folder that has subfolders, you will have a tree explorer for that folder.
            The title bar you would execute the [qw_menu_command Window "Private Setup"] command on would be the title bar of the folder explorer tree's companion detail pane.
		}]
		[p {
			To undo a private setup simply right mouse click on the title bar of the private setup window and execute the menu command [qw_menu_command Window "Default Setup"].
			This will delete the private setup windows and revert to the default setup windows.
		}]
	}
}

/271820130709170230 {
	.title "The sort_interactive script must be run when items are sorted by the interative index."
	.id 271820130709170230
	.tags {error}
	.body {
		[p {
			This error occurs when you attempt to run the sort_items script and the currently selected index is not interactive.
            (Interactive indexes allow you to arrange the order of items using [qw_menu_command Block Move] commands.)
		}]
		[p {
			In many cases, the id index is used when the items are sorted by [qw_term Line] number.
            This happens when there is no interactive index, or the id order (order entered) is more important.
            To check which indexes are available at any time, issue a [qw_menu_command View "Sorted By" "Select Index"] command,
            and in row 2 of the prompt (Sorted By) press [qw_key F3] to see a list of all indexes available.
		}]
	}
}

/271820130423122134 {
	.title "Attempted edit cut to move an item that cannot be moved in this context."
	.id 271820130423122134
	.tags {error}
	.body {
		[p {
			This error occurs when you attempt to move the total row of a list of accounts or journals from one folder to another.
            You cannot move the total row from here because you are one level too deep in your folder hierarchy.
            To move the total row of this folder, move up one level in the folder hierarchy and do it from there.
		}]
	}
}

/271820050404134200 {
	.title "Attempted to append or insert an item in a table with a range set."
	.id 271820050404134200
	.tags {error}
	.body {
		[
			::set ::Html "";
		]
		[h3 "Table: [qw_s_args .window_title]"]
		[p {
			This table is currently configured to select items based on [bold [qw_field_name key]] values that fit within the range specified by:
		}]
		[ul {
			[li {[qw_field_value [qw_s_args .range_begin]]}]
			[li {[qw_field_value [qw_s_args .range_end]]}]
		}]
		[p {
			In most circumstances newly created items will not have key field values that match a selection range.
            New items would be recorded in the database, but not appear on this table.
            This can be very confusing.
            For example, you will press the insert button and it will appear that nothing happened.
            So you will press it again, and again, all the time creating new objects in the database.
		}]
		[p {
			[bold "In order to prevent this confusion it was decided to simply prohit inserts in this situation."]
		}]
		[p {
			This error most often occurs when a ledger of postings is controlled by an account table amount cell.
            For example, if you are viewing a table of customer accounts showing open (unpaid) invoice aging, then each column is a special range of dates.
            Creating a new item with no date specified, or a default date outside the range will cause the disappearing item confusion.
		}]
		[p {
			To insert new rows simply move the cursor (the active blue table cell) left or right to a cell that does not display the total of a range of ledger items (e.g. the account name or description).
		}]
		[p {
            Another far less common scenario occurs if you have manually configured the table range (using menu command [qw_menu_command View "Sorted By" "Select Index"]).
            To insert new rows into this table simply use this command to clear the range.
		}]
	}
}

/271820101122172535 {
	.title "Too Many Columns"
	.id 271820101122172535
	.tags {dialog confirm}
	.body {
		[p {
			The maximum number of columns permitted on a table of accounts is 366.
            The easiest way to create this many columns is by executing a [qw_menu_command View Analysis {Multiple Column Setup}] command.
			For example, configuring one year with daily resolution will create 365 or 366 columns.
		}]
		[p {
			If you are comfortable with reporting in NewViews and you created these columns intentionally, then you can ignore or disable this notice.
		}]
		[p {
			If you are surprised to see this notice and have wondered why NewViews sometimes performs slowly, chances are you created many columns by accident.
			For example, a command to [qw_menu_command View Analysis {New Column} {Actual Minus Budget}] creates three columns at the right side of the table.
            If your screen was too narrow to see these columns you might not have noticed them, and you may have executed the command a few times in frustration.
            Look at the horizontal scrollbar.
            If it's small, this is likely what's happened.
		}]
		[p {
			You can check this by pressing [qw_key "Right Arrow"] and exploring the columns you have.
			Unnecessary columns are easy to delete.
            Position in the column, hold the [qw_key Ctrl] key down and press [qw_key Del].
			([bold Note:] columns created by [qw_menu_command View Analysis {Multiple Column Setup}] are changed/removed by reconfiguring the resolution)
		}]
		[p {
			Remember too that an [qw_key End] [qw_key "Left Arrow"] keystroke sequence will position you in the leftmost column.
			An [qw_key End] [qw_key "Right Arrow"] keystroke sequence will position you in the rightmost column.
			[qw_key "Left Arrow"] and [qw_key "Right Arrow"] also wrap around (e.g. left from the leftmost wraps around to the rightmost).
		}]
		[p {
			Note that version 2.19 introduced a behavior change when creating new columns.
			After columns are appended to the right side of the table, the window is shifted right to the end, and the cursor is placed in the last new column.
		}]
	}
}
/271820050404145940 {
	.title "pgq,debug666"
	.id 271820050404145940
	.tags {error}
	.body {
		[p {
			More information can be found by dismissing the error and pressing [bold F1] for help.
		}]
	}
}
/271820050404145920 {
	.title "Main Document \"$Value\" does not exist. Press [qw_key F3] to select."
	.id 271820050404145920
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091005111405 {Mail Merge}]}]
        }]
	}
}
/271820050404145921 {
	.title "Data file \"$Src\" does not exist."
	.id 271820050404145921
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091005111405 {Mail Merge}]}]
        }]
	}
}
/271820050404134120 {
	.title "Attempted to Mail Merge Block with no block/selection marked."
	.id 271820050404134120
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020080122111307 {Block}]}]
        }]
	}
}
/271820091119115100 {
	.title "Attempted mail merge where it is not supported."
	.id 271820091119115100
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091005111405 {Mail Merge}]}]
        }]
	}
}
/271820091119115101 {
	.title "Attempted Extra Address Name \"[::sargs::get $Settings .address_name]\" for items that don't have extra addresses."
	.id 271820091119115101
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091005111405 {Mail Merge}]}]
        	[li {[link .chm $::qw_manual_file .id 618020091005152230 {Extra Addresses}]}]
        }]
	}
}
/271820091119115102 {
	.title "Cannot produce a PDF file, the PDF Creator printer has not been installed."
	.id 271820091119115102
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091022181606 {Installing PDFCreator}]}]
        }]
	}
}
/271820091119115103 {
	.title "Attempted Email Setup for a workstation database."
	.id 271820091119115103
	.tags {error}
	.body {
		[p {
		}]
	}
}
/271820091119115104 {
	.title "pgq,debug666"
	.id 271820091119115104
	.tags {error}
	.body {
		[p {
		}]
	}
}
/271820091119115105 {
	.title "Email Setup \"$Value\" does not exist. Press F3 to select."
	.id 271820091119115105
	.tags {error}
	.body {
		[p {
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091027124352 {Email}]}]
        }]
	}
}
/271820091119115106 {
	.title "Could not send an SMTP email."
	.id 271820091119115106
	.tags {error}
	.body {
		[p {
        	[link .chm $::qw_manual_file .id 618020091104100150 {Troubleshooting email}] may assist you.
            Failing that, contact your IT person or ISP.
            Failing that, contact QW Page Technical Support.
		}]
		[p {
			For the entire email section of the manual, see [link .chm $::qw_manual_file .id 618020091027124352 {Email}].
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020091027124352 {Email}]}]
        }]
	}
}
/271820091119115107 {
	.title "Email Errors/Problems"
	.id 271820091119115107
	.tags {error}
	.body {
		[p {
        	Check the manual ([link .chm $::qw_manual_file .id 618020091027124352 {Email}]) with attention to [qw_term {Troubleshooting email}].
        }]
		[p {
            Failing that, contact your IT person or Internet Service Provider.
		}]
		[p {
            Failing that, contact QW Page Technical Support.
		}]
	}
}
/271820091119115108 {
	.title "pgq,debug666"
	.id 271820091119115108
	.tags {error}
	.body {
		[p {
		}]
	}
}
/271820091119115109 {
	.title "pgq,debug666"
	.id 271820091119115109
	.tags {error}
	.body {
		[p {
		}]
	}
}
/271820091119115110 {
	.title "pgq,debug666"
	.id 271820091119115110
	.tags {error}
	.body {
		[p {
		}]
	}
}
/271820090709155904 {
	.title "Confirm Fill Column Continue"
	.id 271820090709155904
	.tags {dialog confirm}
	.body {
		[p {
			You are being asked to confirm that you want to skip over an error encountered while doing a [qw_menu_command Tools "Fill Column"] command,
            and continue processing the remaining items.
		}]
		[p {
			The [bold "Yes"] button will continue filling the column for all remaining items,
            stopping at the next error.
		}]
		[p {
			The [bold "Yes to All"] button will continue filling the column for all remaining items,
            skipping all items which cause an error.
		}]
		[p {
            [bold "CAUTION:"] Be careful with the [bold "Yes to All"] option.
            If you know what you're doing, it's a powerful tool.
            If you don't, you could scamble your database in unintended ways.
            Always remember to backup before restructuring data.
            If you mess up, you can restore and no harm is done.
		}]
	}
}
/271820090610151321 {
	.title "Confirm Bookmark Delete"
	.id 271820090610151321
	.tags {dialog confirm}
	.body {
		[p {
			You are being asked to confirm that you want to delete an old, out-of-date bookmark.
			The destination windows have changed in a way that going to the bookmark position is no longer possible
			(likely a window default setup has occurred, or a NewViews version change updated windows in the destination area).
		}]
		[p {
			Chances are if the bookmark was important enough to set, you will want to reset it.
			If you say yes, the bookmark will be deleted and you will remain positioned where you are.

            Keep it long enough to reverse-engineer it's location.
            Manage bookmarks and re-use (update) the old, out-of-date location.

			The bookmark will have to be reset, if possible.
		}]
	}
}
/271820090401104920 {
	.title "Confirm Column Delete"
	.id 271820090401104920
	.tags {dialog confirm}
	.body {
		[p {
			You are being asked to confirm that you want to delete the active table column.
			If you say yes, the column will be removed from the table.
            If you don't know how to get the column back, you should [qw_term Cancel].
		}]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 271820070715140930 {Managing Column Layouts}]}]
        }]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 618020080122111304 {Menu Commands, Windows}]}]
        }]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 150220040804170810 {Modifying Tables}]}]
        }]
		[p {
			The [bold "Delete & Disable Prompt"] button will delete the column, and disable the confirm prompt for all subsequent column delete commands.
            The confirm prompt is initially enabled whenever a table window is first created.
            If you disable it, it will remain disabled until you [qw_quoted "navigate away"], or shut down (i.e. the state is valid only at run-time).
            If you navigate back to the same table, the prompt is re-enabled.
            Finally, if you disable a confirm prompt, it applies only to the single table you do it to.
		}]
	}
}
/271820080326135104 {
	.title "Attempted to select index when no \"object\" is active."
	.id 271820080326135104
	.tags {error}
	.body {
		[p {
			The table you are attempting to set index information is currently not
            observing a database object.
            The index information that can be specified is retrieved from the type
            of data being observed.
            Activate a tree explorer folder, or a table explorer row to cause a
            database object to be observed.
		}]
		[p {
			This error can occur if you are positioned in a title row of a table explorer,
            or if you're access rights don't permit access to the data in question.
		}]
	}
}
/271820080326135105 {
	.title "Attempted a command or operation when no \"object\" is active."
	.id 271820080326135105
	.tags {error}
	.body {
		[p {
			The command or operation you are attempting is in a window that is currently not observing a database object.
		}]
		[p {
			This error can occur if you are positioned in a title row of a table explorer,
            or if you're access rights don't permit access to the data in question.
		}]
	}
}
/271820060331153153 {
	.title "Attempted to create a new class."
	.id 271820060331153153
	.tags {error}
	.body {
		[p {
            You are attempting to move an object or folder into a "root" folder.
            Root folders are reserved for NewViews classes. For example, the root
            Account folder contains all the account classes provided by NewViews.
            The root journal folder contains all the journal classes, and so on.
		}]
	}
}
/271820071024165105 {
	.title "OK to edit active item?"
	.id 271820071024165105
	.tags {error}
	.body {
		[p {
			WOW
		}]
	}
}
/271820071024155207 {
	.title "Access denied."
	.id 271820071024155207
	.tags {error}
	.body {
		[p {
			You are currently logged in as a restricted access user.
            Allowing you to explore the database hierarchy, even for the purpose
            of selecting a pick root, would compromise security.
		}]
		[p {
			If you have unrestricted access to this database, do the following:
		}]
		[ul {
			[li {
				Log out, and then log back in as an unrestricted user.
			}]
			[li {
				Lookup the full path of the object you would like to set as the pick root for the restricted user.
				(The fastest way to do this is to temporarily set the pick root to your intended target -
                the Column Define window will display the the full path.)
			}]
			[li {
				Log out, and then log back in again as the restricted user.
			}]
			[li {
				Enter the full path of the pick root object.
			}]
		}]
		[p {
			Clipboard copy/paste may help, and please note that a better solution to this in under construction.
		}]
	}
}
/271820071021150409 {
	.title "Attempted to change the class of an object that is a class."
	.id 271820071021150409
	.tags {error}
	.body {
		[p {
			The active object is a class. The folder it's in cannot be changed.
		}]
	}
}
/271820050404133610 {
	.title "Attempted to edit a total amount from a collection below."
	.id 271820050404133610
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831134710 {
	.title "Attempted to edit a running balance."
	.id 271820070831134710
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831134813 {
	.title "Attempted to edit a value calculated by a script."
	.id 271820070831134813
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831135216 {
	.title "Attempted to configure a column created by a script or automatic analysis commands."
	.id 271820070831135216
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831135521 {
	.title "Attempted to delete a column setup that was created by a Window Default Setup command or script."
	.id 271820070831135521
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820060523132125 {
	.title "Settings must have a name."
	.id 271820060523132125
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831140432 {
	.title "Attempted to rename a column setup that was created by a Window Default Setup command or script."
	.id 271820070831140432
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820060523132141 {
	.title "Attempted to rename the *** Default Settings ***"
	.id 271820060523132141
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820060523111245 {
	.title "A setting with name \"$Name\" already exists."
	.id 271820060523111245
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820060523111246 {
	.title "Attempted to delete the *** Default Settings ***"
	.id 271820060523111246
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831141231 {
	.title "Settings copied. Name the new setting and edit columns as required."
	.id 271820070831141231
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831140433 {
	.title "Attempted to rename a setting that was created by NewViews."
	.id 271820070831140433
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831143613 {
	.title "Attempted to edit a setting defined in a folder \"above\"."
	.id 271820070831143613
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820070831135522 {
	.title "Attempted to delete a setting that was created by NewViews."
	.id 271820070831135522
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820050404134435 {
	.title "Attempted a block operation with no tag specified."
	.id 271820050404134435
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271800000000000000 {
	.title "pgq,debug666"
	.id 271800000000000000
	.tags {error}
	.body {
		[p {
		}]
		[p {
		}]
		[p {
		}]
	}
}
/271820050404133430 {
	.title "Attempted to activate a folder before all folders in the path to it have been previously activated."
	.id 271820050404133430
	.tags {error}
	.body {
		[p {
			In most cases, NV2 creates a [qw_quoted "private"] window (desktop) for each database object.
            For example, you may have a hierarchy of journals of any given type. Activating a journal
            deep in the hierarchy may cause this error.
		}]
		[p {
            The reason for this is a long-winded technical discussion beyond the scope of user documentation.
		}]
		[p {
            To avoid this error, simply activate the [qw_quoted "root"] folder of the type selected and [qw_quoted "walk down the staircase"]
            one step at a time, activating each folder in the path. Once the windows for each folder in the path are setup, this error will never occur again.
		}]
	}
}
/271820050404134530 {
	.title "\"$SearchForIndex\" index does not support \"$IsHitPortion\" selection."
	.id 271820050404134530
	.tags {error}
	.body {
		[p {
			You have attempted to select an index that does not exist.
		}]
		[p {
            Many NV2 indexes have two parts to their specification. The first part is the sort order and the second part is the selection.
		}]
		[p {
            For example, total accounts might be sorted by name and description (among other possibilities).

            It is also possible to select a total account index that displays only the [qw_quoted root] total accounts
            (i.e. total accounts that total no further - an example would be the [qw_quoted PROOF] account of a set of books).

            It is convenient to sort total accounts by name or description, but it would be overkill to provide all
            root total accounts sorted both ways. It would take addition time and disk space, and one sort order is enough
            to allow you to find all root total accounts.

		}]
		[p {
			When you click on a column title to sort a table by that column value, the sort order component
            of the index is replaced by the field for the column. If there is no index for that sort order and
            the current selection then this error is the result.
		}]
		[p {
			To view all indexes for a given table execute the [qw_menu_command File Sort "Select Index"] command
            and in the Index Value cell of the window presented press [qw_key "F3"].
		}]
    	[p {
        }]
        [ul {
            [li {[link .chm $::qw_manual_file .id 857720050103095655 {[qw_menu_command File Sort "Select Index"]}]}]
            [li {[link .chm $::qw_manual_file .id 314120050321075429 .bookmark 314120050404162935 {Tips and Techniques}]}]
        }]
	}
}
/271820121105164945 {
	.title "Attempted to configure a HISTORY table that is controlled by a cell range."
	.id 271820121105164945
	.tags {error}
	.body {
		[p {
			The history table you are attempting to configure is managed automatically by a cell in the [qw_quoted "controlling"] account table window.
		}]
		[p {
            Account tables used to display amounts or balances can show the corresponding summary history items in a detail window [qw_quoted "below"].
            The history items displayed are selected from the active account table cell ([qw_quoted "range"]), respecting the tag, begin date and end date specified for the account table cell.
		}]
		[p {
			Note that this error only appears when you attempt to configure the information specified in the account table cell
            (i.e. Tag, Begin Date and End Date).
            You are expected to configure the other history table settings to view the data in any detail desired
            (i.e. Resolution, Representation and Display Order).
		}]
		[p {
			A very useful example would be to explore a Multiple Period Analysis, say set for monthly resolution, with the detail history window set for daily resolution.
            As you active account table cells, the history table will display a row for every day of the selected month.
			There are many interesting and useful variations on this theme.
		}]
	}
}
/271820050404134730 {
	.title "Attempted to sort a table that is controlled by a cell range."
	.id 271820050404134730
	.tags {error}
	.body {
		[p {
			The table you are attempting to sort is controlled by a cell range [qw_quoted "above"].
		}]
		[p {
			An example will help explain this error. Account tables used to display ledger balances
            often show the corresponding ledger items in a window [qw_quoted "below"]. The ledger
            items displayed are selected from a [qw_quoted "range"], sorted by date, respecting the
            begin date and end date specified for the account table cell. (Note, in general, the account
            table cell could be configured to display ledger items in a range of reference numbers,
            or description values or reconcile values, etc. - and in these cases the ledger items would
            be displayed sorted by reference numbers, description values, or reconcile values, etc.)
		}]
		[p {
			You might ask why not just sort the items selected from the date index by another column value.
            NV2, in many respects, resembles a spreadsheet, but it's not. NV2 is a database application
            and when you view items sorted one way or another, you are viewing them using a database
            index - a persistent database index, maintained dynamically on disk. When you activate
            an account table cell to view the postings that sum to the cell, you may access thousands or
            millions, or more, ledger items.
		}]
		[p {
			For NV2 to sort these items by something other than the date, on demand would, in most cases,
            be an intolerable delay and render the feature useless. On the other hand, maintaining the
            database indexes to provide the ability to display items in a date index range by every conceivable
            order would also introduce intolerable delays, and consume vast amounts of disk space.
		}]
		[p {
			Note also that the column the cell is in can be configured to display, for example,
            debit amounts. The ledger below will then display only debit postings. The same is true for credit
            amounts, or open or closed amounts. Finally, continuing the example of an account table above and
            a postings table below, the account cell can be configured to display amounts for a particular
            tag (e.g. financial, order or budget) and the postings table will display only the postings
            with that tag.
		}]
		[p {
			To sort a table by any column, position on a cell above that is not configured to display a range
            (e.g. name or description).
		}]
	}
}
/271820050407143044 {
	.title "The popup audit table cannot be sorted. Items appear in order created."
	.id 271820050407143044
	.tags {error}
	.body {
		[p {
			The audit trail displayed in this context is for an individual database object.

            It displays only the audit activity for the currently activated object, in the order the
            changes occurred. If you have access rights to the audit for the entire database, you
            can navigate there and display audit records in any order.

		}]
	}
}
/271820050422150433 {
	.title "The printer \"$Printer\" does not exist on this system."
	.id 271820050422150433
	.tags {error}
	.body {
		[p {
			Under construction.
		}]
	}
}
/271820050430113519 {
    .title "The F3 key has no purpose in a table's title row."
	.id 271820050430113519
	.tags {error}
    .body {
		[p {
			You were positioned in the title row of a table when you pressed [qw_key F3].

            You can use [qw_key F3] when you are on a non-title row to select values
            for fields, but [qw_key F3] serves no purpose in the title.
	    }]
	}
}
/314120051220092644 {
    .title "Confirm Default Setup"
	.id 314120051220092644
	.tags {dialog confirm}
    .body {
    	[p {
			You are being asked to confirm that you want to replace all windows
            under the current window with their default setups.
        }]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 150220040804170150 {More on default window setup.}]}]
        }]
    }
}
/271820110819115050 {
    .title "Confirm Private Setup"
	.id 271820110819115050
	.tags {dialog confirm}
    .body {
    	[p {
			You are being asked to confirm that you want to create a new private set of windows for the active folder.
        }]
    	[ul {
        	[li {[link .chm $::qw_manual_file .id 271820110819115050 {More on private window setup.}]}]
        }]
    }
}
/271820060403145544 {
    .title "Attempted to select invalid index."
	.id 271820060403145544
	.tags {error}
	.comment {Index Id == [qw_quoted "[qw_s_args .invalid_index_id]"]}
    .body {
		[p {
			The index you tried to select is a [qw_quoted "place holder"], used to group valid indexes [qw_quoted "below"].
            Click on the [qw_quoted "+"], if you haven't already done so, and select a real index from below.

	    }]
	}
}
/271820050404134250 {
    .title "Attempted an Edit Quit command when no row is active."
	.id 271820050404134250
	.tags {error}
    .body {
		[p {
            You can use the [qw_menu_command Edit Quit] command when you are on a non-title row to quit any changes
            and restore all fields to their original values.
	    }]
	}
}
/271820050404134251 {
    .title "The Edit Quit command has no purpose in a table's title row."
	.id 271820050404134251
	.tags {error}
    .body {
		[p {
			You were positioned in the title row of a table when you issued an [qw_menu_command Edit Quit] command.

            You can use the [qw_menu_command Edit Quit] command when you are on a non-title row to quit any changes
            and restore all fields to their original values.
	    }]
	}
}