Hope I have understood your question.
A browse lists the result of the query (customer).
The button needs to know the contents of a line in the browse.
So, the code for the button (ON CHOOSE OF BUTTON) might be:
DEF VAR cust_num LIKE customer.cust-num NO-UNDO.
IF AVAILABLE...
I would not choose the recid (or the newer rowid for that matter) for such a purpose. If the database 1 is deleted and reloaded with data, there is a good chance all the recids will be different from the original ones.
Why don't you create the entire record - or at least the index field values...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.