|[ < Prev | Contents | Next > ]|
[ Procedures ]
To view the details of a transaction which is being entered or has been entered.
Used when transactions are to be deleted and for debugging purposes - both for the Max2 software itself and for charging rules.
State file has been built.
Higher operator levels are required for different methods of access. These are noted below where appropriate.
Details of individual transactions are displayed in thewindow. This shows various "header" information about the transaction such as which file it is in (start-of-month or daily), its offset into the file, its type and so on and the contents of each of the fields in the transaction.
The details of thewindow are discussed later in this topic, but first the different methods of opening transactions in it are described.
Thewindow can be used to display the details of either transactions which are being prepared for posting or transactions which have been posted. The methods of displaying each of these types are different and the details shown in the window are also slightly different.
This section describes the various methods used to locate a transaction to be displayed.
On the(see Glider Flying Logsheet Entry) and (see Power Flying Logsheet Entry) windows it is possible to see the details of the transaction which is being prepared for posting. This can be particularly useful if the calculated values for times and prices of the flight are not as expected - looking at the transaction details can show how the charging rules are being applied to the transaction.
This method requires at least Basic Entry operator level (for glider flights) or Full Entry (for power flights) to open the appropriate flight entry window.
In order to see the transaction details choose thebutton.
As the details are changed in theor the corresponding fields in the window are updated.
This is the most direct method of viewing a transaction which has been posted to a transaction file. It applies in the case where the file (start-of-month or daily) and the offset of the transaction into the file are both known. Typically, this information is obtained from an error message, usually during a state file rebuild (see Building State Files).
This method requires Full Entry operator level.
In the main window's menu choose| . The window is displayed. Choose the option button for the file containing the transaction and type in the offset of the transaction as a decimal number.
If the transaction offset entered is incorrect then very unpredictable things may happen.
Chooseand the window for the specified transaction is displayed.
This method applies when it is necessary to access one of the last thirty transactions in the month. Note that even the last start-of-month transaction is not accessible by this method once thirty daily transactions have been entered.
In the main window's menu choose| . This displays the window. Expand this window or scroll it backwards to view the required transaction then double click on it to open the window.
This method can be used to access any transaction in the month.
In the main window's menu choose| . This displays the window containing all the non-deleted transactions for the month. Any transaction can be found by scrolling up and down in this list. When the required transaction is found double click on it to open the window.
This method can be used to find a transaction in a short list selected from the transactions in the month.
In the main window's menu choose| . This will display the window. Fill this in to select a suitable subset of the month's transactions as described in Transaction Selectors. Note that you can only select transactions from the current month; if you choose a different start or end month you will get a dialog box warning you and then the appropriate transactions from the current month are shown.
Double click on the transaction of interest to open thewindow.
This method applies to accessing transactions for an individual account. Open thewindow (see Displaying Proper Account Transactions). Double click on the required transaction to open the window.
If an error occurs during a state file build (Building State Files) this method allows access to the erroneous transaction.
If the option to stop the state file build on errors has been selected then either the Locate Transaction method described above can be used or the state file build can be repeated with the option to log errors to the error log window selected.
The transaction causing an error shown in thewindow can be displayed by either selecting one of the lines in the error message and choosing the button or by double clicking on any line in the error message.
This method is basically a short-cut for using the Locate Transaction method.
This section describes thewindow, once it has been opened using any of the methods described above.
At the top of thewindow are a number of controls describing the details of the transaction.
This box indicates which file contains the transaction. It is "1" for start-of-month transactions, "2" for daily transactions and blank for transactions which have not been posted (e.g., glider or power flight transactions being entered).
This box displays the offset (position) of the transaction into the relevant file. It is a decimal number. This number can be used to find the transaction again using the Locate Transaction method described above.
For transactions which have not been posted this box is blank.
These boxes show the internal number used to represent the type of the transaction and a text representation of the same value.
The number of the rule set which applies to this transaction type. Set to -1 for transactions which do not have rule sets, 0 for glider flight transactions and 1 for power flight transactions.
Below the transaction details are the fields which make up the body of the transaction.
First the fields which are intrinsic to the transaction (actually stored in the transaction file) are displayed, followed by the fields which are defined by the intrinsic rules and final the fields which are computed by the charging rules. Of course, for many transaction types there are no charging rules and therefore no intrinsic rule or computed fields.
The individual columns in the table of fields are described below. Note that if a column is not wide enough for the value in a field to be displayed fully it is possible to see more of the field by resizing the column. Do this by dragging the separator bar between the column headings.
The number of the field in the transaction. The first field is field zero.
The name of the field, as used in the program and in the charging rules.
The state of the field. A combination of the following letters:
Only certain combinations of these letters should actually appear: P, PD and PCD.
The type of information stored in the field.
The length of the field as it is stored in the transaction, in bytes.
The value (contents) of the field. How this is formatted depends on the type of the field.
Some field values are "binary" values - that is, more complex structures interpreted by the Visual Basic code in Max2. These are shown as hexadecimal byte values.
Thewindow has three buttons at the top right.
(or ) is used in procedure Deleting or Undeleting Transactions.
displays the window which lists the rules which have been applied to the transaction.
is used to apply the same transaction to a number of accounts, see Duplicating Transactions.
Deleting or Undeleting Transactions
Deleting or Undeleting Multiple Transactions
Displaying Proper Account Transactions
|[ < Prev | Contents | Next > ]|