.title "Gui" .id 314120050317103808 .tags "manual" .body { dummy } /314120050317104419 { .title "OK to perform default setup of new database explorer?" .id 314120050317104419 .tags {dialog confirm} .body { [p { If you confirm that you want to perform a default setup of the explorer in the right or bottom pane, a number of windows will be set up in their default configuration. You are asked for confirmation because this operation can take a while and you may have to wait. This setup operation generally occurs only the first time you visit a particular area of the database and does not have to repeated the next time. }] [p { The amount of time that the operation will take varies, and depends on the nature of the window being set up. That is because the NV2 window system is [qw_term "polymorphic"] and [qw_term "context sensitive"]. What this means is that windows are set up according to the types of the objects being viewed. }] [p { So, if for example, the right pane contains reports, then report windows are set up. In turn, these reports contain accounts, so under the report windows, account windows are set up. Under the accounts, ledger and/or transaction windows are set up. and so on. }] [p { In each step, the items will also vary. For example, when setting up account windows under the reports, the individual account windows may vary because there may be accounts of different types on the same report. The window for a total account differs from that of a general account, or a vendor or customer account, and so on. In turn, tranactions under an account will vary, as for example, a customer will likely have invoices, deposits, and so on. }] [p { The setup operation will not attempt to create all possible windows as that would require a complete [qw_term traversal] of the entire database. So from time to time, as you are exploring the database, you might notice windows being set up. This will occur the first time you visit a particular area for which the windows have not been previously configured but will not happen again when you re-visit the same area. }] [p { The NV2 window system adjusts automatically according to the objects being viewed. It also remembers where you were so that when you visit and re-visit different areas of the database you can always pick up where you left off. We believe these conveniences out-weigh the initial delay faced when the windows are originally set up. }] } } /314120050331102740 { .title "The system sets the screen XXX field and it cannot be changed." .id 314120050331102740 .tags {error} .body { [p { The [qw_field_name [qw_s_args .field_path]] field of a screen is set by the system and cannot be changed by a user. }] } } /314120050411102144 { .title "Could not delete a block." .id 314120050411102144 .tags {error} .body { [p { An error occurred while attempting to delete a block of rows from a table. The reason for the error should be described in other errors below. }] [p { No rows were deleted. Deleting a block is an all-or-nothing operation. Either the entire block is deleted, or nothing is deleted. }] } }