No records found message

[Terry Pickering]

Is there away to suppress or trap the "No records were found matching
index/selection values" from displaying?

I have a primary record with detail records in a cluster that the user
finds, then executes a designer procedure. At the end of the designer
procedure, I PUSH NEXT to get the next record.

I've tried putting an optional on the GET statement and testing for
accessok, but still can't trap it. I'd like to change it to say something
like "No more records to change" since normally they are retrieving the
records sequentially and they hit this on the last one.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Terry Pickering        Consultant Extraordinare
Monday and Friday        Tuesday - Thursday
Portland                 Eugene
(503) 245-7178           (541) 687-3416
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.