a method I read about and now use is that, before constraining, open a new window then set error capture on and if no records found, close the window. You'll be back on your set before the constrain.
Another alternative that avoids the "window re-size bug" caused by using New Window on a Windows platform:
Create a new layout and base it on a different Table Occurrence than your first layout, but with the same data source table. Make a script that:
Freezes the window
goes to this new window
Set error capture
use get (found count) to check for records If none found, go back to your original layout.
Since the layout is based on a different table occurrence, the find will not affect the found set of your original layout.
Dear Stella Luna
Tried your method and got it to work. Had to play
around with the order of the statements and placed the
new window far enough off screen that it isn't seen.
A Custom Dialog Box tells the user that no records
were found. The original Found set is still available in
the table layout
Thanks for your help. Sincerely, CountryBoy1
I got the idea from Stella Luna to work, but in reality, I think I'm
doing about what you suggested. I don't freeze the original
window but I think I'm doing everything else in the order that
You have helped me before and I appreciate it.