Re: list2 [message #2554 is a reply to message #2553] |
Tue, 22 June 2010 08:29 |
AJM
Messages: 2368 Registered: April 2006 Location: Surrey, UK
|
Senior Member |
|
|
You haven't read what I wrote. If you start with a LIST1 screen which shows a number of entries from the parent table, and this LIST1 screen contains a navigation button which transfers control to a LIST2 screen, then you cannot hide or show the navigation button depending on the value of this status field. The LIST1 screen will be showing several records, and some of these records might have a FALSE status while others are TRUE. You have to wait until *AFTER* one or more parent entries have been selected, *AND* the LIST2 navigation button has been pressed (remember, there may be other navigation buttons) before you can decide whether the LIST2 task is valid or not for a particular parent record. This processing must be inside the LIST2 task, not the one which calls the LIST2 task.
I repeat, you cannot prevent the LIST2 navigation button from being pressed, you can only decide if the action is valid *AFTER* it has been pressed.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|