Getting Started-JetNet

In this lesson, you enhance the Distributor Orders (dstord.scr) screen so users can query the database for a specific distributor record. You learn about Panther widget properties and how to set them appropriately.

Properties can be set and changed locally for the current screen and its components, and globally for objects throughout the application:

• Properties for some objects should be set on a screen-by-screen basis, because the behavior or appearance of the object depends on how it is used. For example, on a data maintenance screen, you might want to enforce data entry in a field by setting its Required property to Yes, while on another screen, the equivalent field does not have the same requirement.

• Objects throughout your application can inherit their property settings from the repository. For example, you might set a widget's validation, font specification, size, and format in the repository. All widgets that inherit from this repository object have the same appearance and behavior.

In this lesson, you set properties that allow users to search the database for a specific distributor by entering an identification number. The transaction manager automatically generates the appropriate SQL query statement based on this input, submits the input to the middleware API, and ultimately returns the desired distributor data to the client.

In this lesson you learn how to:

• Set widget properties on both the client screen and its corresponding service component.

• Specify a particular widget to act as a query field.

• Test the resulting query screen by searching for specific distributor records.

  ---

1. If necessary:

   • Reactivate the application, invoke the editor, and connect to the middleware.

   • Reopen the client screen dstord.scr in client.lib and the service component dstord.scr in server.lib on the application server.
     

You can define the appearance and behavior of screens and widgets through the Properties window. If the Properties window is not open in the editor workspace, open it with one of these actions:

• Double-click on a widget or on the screen.

• With focus on the screen or a widget, press Enter.

• Choose ViewProperties Window.

More About the Properties Window

The Properties window lets you easily view and set properties for all Panther objects—for one object at a time or for multiple objects simultaneously. If multiple objects are selected, the Properties window displays those properties that are common to all, so you can assign the same font, colors, and formats. If the selected objects have different values for a given property, three questions marks (???) are displayed as the property value.

When no widgets are selected, the Properties window displays the properties of the current screen.

Properties are grouped by category under descriptive headings on the left. Initially, the properties list is collapsed and displays only headings.

2. In the Properties window, choose .

   All property headings expand, displaying the properties and their respective values on the right. To change a property value, select the property and type or select a new value in the Setting field/option menu of the Properties window.

   You can also expand and collapse headings individually. To expand or collapse a single heading, simply click it.

3. Choose .

   The properties list collapses, displaying only the property headings.

   No matter how you set a property, you can reverse any change with EditUndo or .

The next several steps show how to set a property on a widget at the screen level. You need to set a Database property for the distrib_id widget so that users can obtain information about a specific distributor and its orders via its ID number. The ID number is used to search for a matching record in the database.

4. On the client screen dstord.scr, select the single line text (data entry) widget distrib_id, which is adjacent to the Distrib_id label.
   

5. In the Properties window, select the Database heading.

   Database-specific properties are displayed.

   

6. Under Fetch Data, select the Use In Where property.

   An option menu is made available in the Properties window. Here you select from a list of predefined values.

More About Setting Predefined Property Values

You can set a property with predefined values in several ways after you select it:

• Click directly on the displayed property value to scroll through all possible values.

• Type the initial character to specify a value. For example, type y for yes or n for no.

• Select values from the option menu.

7. Click on the option menu to display its drop-down list, and select Yes. Press Enter or choose OK.
   

   Yes tells Panther to use the field in the WHERE clause of the database query. When you change the Use In Where property to Yes, two other changes occur:

   • Related subproperties display, including the Operator property. By default, the Operator property is set to = (equal sign).

   • The Use In Where property value no longer displays in reverse video. This indicates that the inheritance link no longer exists for this property—in other words, the property no longer gets its value from the repository.

     Database property settings give Panther's transaction manager the information it needs to build an SQL statement to fetch, display, and update the requested record. At runtime now, when a distributor ID is entered in the distrib_id widget and a View or Select command is issued, Panther searches the distrib_id column in the distributors database table for a record with a matching ID.

More About Inherited Property Values

The Properties window uses reverse video to show which property settings are inherited. The Inherit From property under the Identity heading identifies the source of inheritance. Objects within the repository that are imported directly from a database have their Inherit From property set to @DATABASE.

Screens that are created by the screen wizard inherit screen, push button, and grid property values from prototype wizard-specific repository entries, while labels and data entry-type widgets inherit their property values from database-derived repository entries.

8. With focus on the dstord.scr client screen, choose FileSave or .

   The screen is saved to client.lib on the application server.

It is important to keep the service component and its calling client screen synchronized, because the service component must perform the actual passing of data to and from the database server. In general, all property settings that affect processing of data must be made to both the client screen and its corresponding service component.

9. Repeat steps 5 through 8 for the distrib_id single line text widget on the dstord.scr service component.
10. Choose FileSave or .

The service component is saved to server.lib on the application server.

View specific records

Now test the client screen to find a specific distributor's records.

11. Bring focus to the dstord.scr client screen.
12. Choose FileTest Mode or .

The Distributor Orders screen opens in test mode.

13. Enter 3 in the distrib_id field.
14. Choose .

    The distributor record that contains ID number 3 displays.

    

15. Choose .

    The Reset button executes a Close command, which closes the search transaction and clears all fields of data so that you can search for another record.

16. Enter 7 in the distrib_id field.
17. Choose .

    The distributor record that you added to the database in Lesson 9 displays and can be edited.

18. Type 5551234567 in the Phone field.
    

19. Choose .

The service distributor_u is called to update the database with the changes.

20. Choose .

The transaction closes. You can try all the buttons on the screen. However, you must remember to choose Reset to close each transaction and clear the fields.

Note: Using the Delete button on this particular screen deletes the selected distributor and its orders. However, this also orphans records in the order_items table that are associated with the deleted orders records. Therefore, you should not delete distributors via the dstord.scr screen.

21. Press Shift+F5 (Esc twice or choose OptionsEditor) to exit test mode and Return to the editor.

    ---

In this lesson, you created a query screen that lets a user enter data that is used to search for a specific database record. You did this by performing these tasks:

• Define a query field on both the client screen and service component by setting their Use In Where property.

• Test the resulting screen by entering search criteria.

What did you learn?

You learned:

• The Properties window lets you set an object's behavior.

• Inherited property values can be selectively overridden, without affecting inheritance links for other properties.

• It is important to keep client screens and their corresponding service components synchronized with the same data entry widgets.