General information
Category:
Forms & Form designer
Ok, I didn't realize you needed this to work for other buttons, too. One possibility might be to change the strategy and validate all the fields when the user saves. I don't have any other ideas, sorry.
As to the PUTM, I pay for it myself so I have full control over it. I just renewed at $150CDN for 18 months. Not sure what I paid in USD, but I know the exchange rate works in our favor. :)
Michelle
>That will certainly help in a lot of situations, but unfortunately the button in question isn't always a cancel button. In some situations it launches a value picking form, and in others it might launch a "define new..." form. In all of these situations, we are fighting with the validation of the current value.
>
>We used to have a PUTM, but when the prices went up my boss didn't want to resubscribe us. Of course, I'm the one that uses it not him.
>
>
>>Here's an answer from Nigel to this same question:
>>
>>"First line of valid: If LastKey()=27 Return .T. - this should do it. Your cancel button will need to be cancel=.t. (I think it will work then)."
>>
>>If you can swing it, a PUTM is great for the ability to search on stuff like this...
>>
>>Michelle
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only