When a QBFNEXT, QBFPREV, QBFABS, QBFFIRST, or QBFLAST event occurs, the Menu of an MDI frame sends a Message to the mdiactive window with the corresponding Event. However, this does not trigger a read event and Savewarn is not in effect if changes are made in one of the rows.
Is there an easy way to change this behavior? Should the commuter module of the MDI frame first be called, checking to see if the event is one of these five before sending it on? I am somewhat surprised that a record read from a cursor is not subject to the same logic as a record whose key is entered manually. Am I overlooking something?
Checkout IOOPTIONS - Specifies whether QBF events force a Read event.
World leaders in all things RevSoft
Thanks. That did it.
I had run across this long ago but forgotten about it. It might not be a bad idea to have a link to it in the documentation where QBF is discussed.
Revelation should set up a documentation wiki that users can edit, in order to improve documentation and make those hard to find features, well, easy to find.
That would be a great resource.