| Home | Previous Lesson: Pipeline Object At Work Next Lesson: Where To Use a DataStore? |
Do you remember, in the transaction window, we are using a hidden DataWindow control to print the transactions report. This is because, we are using different DataWindow controls dw_tran_header and dw_tran_detail for transaction entry and printing those two DataWindows together as we see on the screen isn't possible.
In some places we also have used hidden DataWindow controls to make sure that user is not adding a existing product_no again.
In all these areas wherever we are using hidden controls, we aren't really coding for clicked, rButtonDown events. Because, those are hidden, user can't click on them. That means providing any visual related events and functions are meaningless. What we mean by "Visual" in this context is, any user interaction related event and functions.
With version 5.0, PowerBuilder came up with a new object called DataStore. A DataStore is a non-visual DataWindow control. It's like a DataWindow control except that many of the visual properties associated with the DataWindow control aren't available at DataStore object. However, because you can print DataStores, PowerBuilder provides some events and functions for DataStores that pertain to the visual presentation of the data.
| Home | Previous Lesson: Pipeline Object At Work Next Lesson: Where To Use a DataStore? |