Design › Designing Client Procedures › Lesson Activity › eGolfer Home › Add Procedure Step Use Statements for Servers › Maintain Scoring Record

Maintain Scoring Record

When calling the Maintain Scoring Record server procedure, we have to tell it which golfer the scoring record is for. Thus, in addition to it requiring information about the scoring record, it also requires information about the golfer that the scoring record is for. We will reuse the golfer views we just added for the Maintain Golfer server procedure step, but we will use Match and Copy to create the new views for the scoring record. The Maintain Scoring Record server has no export views.

Follow these steps:

1. Repeat the steps we used to add a procedure step use statement for the Maintain Golfer procedure step to add a procedure step use statement for the Maintain Scoring Records procedure step. However, when matching views, use the existing golfer from EGOLFER HOME instead of adding a new golfer, and accept the name for the new scoring record import view created through the Match and Copy dialog import.
2. Your action diagram should now look like the following example:

   

   If your action diagram does not look like the previous example, take time now to correct it. You should only have two import views, one of import scoring record and the other of import golfer. The order of the two views is not important; in other words, you can have import golfer and then import scoring record. In the export views you should only have one view, that of the export golfer. All three of these views should have the same attributes in them as shown, but the order of the attributes within the views is not important. Likewise, the order of the two USE statements is not important either; eventually we are going to move them down into event handlers.

   Correcting the views is relatively easy to do. Here are some tips on how to fix them:

   • If you have the correct three views and the only thing wrong with them is you mistyped or forgot to enter a name for each view, simply double-click the Entity View name and correct it.
   • If you have a duplicate import golfer, then it is probably because you did not reuse the import golfer that was already there and instead created a new golfer using Match and Copy. If that is the case, the second golfer cannot be named import (since we already had a golfer named import) and you had to either misspell the name import to add it or you did not give it any name at all. Furthermore, the use statement of the Maintain Scoring Record server probably references this extraneous view.
   • To fix this problem, first you have to change the reference to it; then you can delete it from the views. Double-click the reference to it in the USE statement. In the MAINTAIN SCORING RECORD Import View Matching dialog, select IMPORT GOLFER from under the MAINTAIN SCORING RECORD Import View. You should see that it is matched to the incorrect view. Select the Unmatch push button to unmatch the two views. Then, from the Possible Supplying Views shown in the bottom panel, select IMPORT GOLFER and then select the Match push button. Then select the Close push button. It should now be matched to the correct import view and you can delete the extra view by selecting it in the IMPORTS: and then selecting the Delete… icon from the Toolbar.

     Your diagram should now look the same as the example shown, notwithstanding the order of the views or statements.

3. For procedure steps, and particularly for client procedure steps, the import views and the exports view usually need to be identical. In fact, the occasions for when they are not identical are so rare it is not even worth thinking about. For client procedures steps, then, make your import and export views the same.

   To make these the same, we need to copy the import scoring record to the EXPORTS. Select import-scoring record, then press F8 on your keyboard and with the cursor (which now resembles a hand), select EXPORTS. Name the copied import view export, and select the OK push button.

4. Save your model.