December 5, 2006
Brian Hancock wrote: When I saw Don's suggestion I thought it can't have been that simple
And you were so right! :-[
I think the problem with the simple approach is that (and I am only guessing here) I think that in DP there is a cascading mechanism for triggering formula evaluation.
It seems clear there is some order to the evaluation of the formulae, but what I don't understand is why that does not mean that you can never go back in the sequence of buttons. You can go back as long as you don't choose the last button. And if I add a later button, a fourth, instead of three, for example, I can then choose the third button and go back and choose the first or second to replace it, but now the fourth button locks its value in place.
For instance you can see a similar concept in the attached test.str... If you create a record and enter data in the "New" field, then every time you edit the record the previous value appears in the "Old" field, so instead of the formula in the "Old" field grabbing the new data , it points back to the previous new data. The way this is done is that the formula in Old goes thru a recursive link to the same record looking at the value in New. You can use this to force a field into having its first entered value to be unchangeable. On the attached STR once you have entered a value into the "Sticky" field it will be unchangeable, but you can edit it at any time as long as it is blank. The recursive link lets you do all sort of curious things.
I found your example anything but "blah" (as you named the panel). I've never done a recursive link directly to the panel I'm working in, only indirectly. The results are very interesting! The ease of recursive links is in my opinion one of the exceptional values of DP.
Don Codling WP 12.0.0.602 DP 2.6x Windows XP home, SP2 512 MBytes RAM _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
