Hi Brian,
Thanks for your comment about going the DPMouse route & the str - yes
the recursive link can do many fascinating things.
I seem to recall when trying to solve a problem in the past, realising
that when entering data into a field, DataPerfect seems to hold it in a
temporary state "somewhere" until you move to the next field or do a
save. Until then, the field seems to hold its previous value.
Maybe something along the lines of Don's thinking but using recursive
links is the way to look. I will experiment further when I get a chance!
Regards,
Michael
Brian Hancock wrote:
Hi Michael,
I think the DPMouse will be easier... When I saw Don's suggestion I
thought it can't have been that simple as I spent some time getting it
working, and that would have been my starting point... 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. The concepts of the formulas were quite simple
except that by using a recursive panel link I think I intervened in
that order process, you can look at something back in time, for
example picking up blanks from a field than now contains an X.
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.
Regards
Brian
----- Original Message ----- From: "Michael Iannantuoni"
<[EMAIL PROTECTED]>
To: "DataPerfect Users Discussion Group" <[email protected]>
Sent: Wednesday, December 06, 2006 7:42 AM
Subject: Re: [Dataperf] Nearly Radio Buttons!
Thanks for confirming that Don,
I'll stick for now with my conditional ACII 249's & DPMouse.
Best wishes,
Michael
Don Codling wrote:
December 5, 2006
Rats, I thought I had an answer for you.
My set up works the same as yours does. On my system at least, you
can change back and forth unless the last button is selected; then
no more changes apply, without first deleting the letter in the last
button.
I played with this a bit, because I hate have a glitch that I can't
resolve, but found no ready answer.
My first thought was to set up a dummy button as the last button.
But if I hide that button, then DP treats the second last as it did
the last, with the same problem results.
Then I tried putting a "" formula in the dummy button, but if I
enter an X, it stays there. It seems that entering something in
another button is not recognized as a change.
I would think the formulae are applied in the order in which the
buttons are set up, so that all the other buttons are cleared again
before you get to the last button, except that would mean you could
never go back. However, I can go back, until the last button is
selected. So I'm baffled.
A dummy button will make the others work, but if it is select ed, it
kills the system, as it were.
Don Codling
WP 12.0.0.602
DP 2.6x
Windows XP home, SP2
512 MBytes RAM
Michael Iannantuoni wrote:
OK so now I am puzzled because I don't see any difference between
what you are doing and what I have done - test STR attached
Michael
Don Codling wrote:
December 5, 2006
I assume you have missed something or have something complicating
your result, because I can go up and down the row and it changes
every time I enter "Y" in a new button.
P1F4 formula
IF (P1F5 = "Y")
OR (P1F6 = "Y")
THEN "" ELSE "Y"
ENDIF
P1F5 formula
IF (P1F4 = "Y")
OR (P1F6 = "Y")
THEN "" ELSE "Y"
ENDIF
P1F6 formula
IF (P1F4 = "Y")
OR (P1F5 = "Y")
THEN "" ELSE "Y"
ENDIF
I have done this in some data bases with the alternative to "Y"
being "N" rather than a blank. It's quite flexible that way.
As well each of them is set to "Initialize at Create/Save/Change",
so it changes immediately a choice is made. After the first
record, that means that Radio button 1, P1F4, is initially
selected, but then another selection returns that to blank.
The first button I touch in the first record, I can put anything
in it, and get "Y". Thereafter, buttons will only accept a "Y".
To make a change after a record has been saved, you have to go to
edit, which means your first key stroke won't do anything.
Don Codling
WP 12.0.0.602
DP 2.6x
Windows XP home, SP2
512 MBytes RAM
Michael Iannantuoni wrote:
Thanks Don,
That works OK up to a point: the problem I have is that if P1F6
is set to "Y", it must be unchecked before either of the two can
be checked or am I doing something wrong?
Michael
Don Codling wrote:
December 5, 2006
If by radio buttons you mean fields in which if one is on the
others are off, it seems fairly simple to me, perhaps because I
deal in simple structures.
I have created a test database which has U1 fields P1F4, P1F5
and P1F6.
Each of them has a formula associated with it, in this form (for
P1F4)
IF (P1F5 = "Y")
OR (P1F6 = "Y")
THEN "" ELSE "Y"
ENDIF
these are set to change when modified.
If you enter anything in any one of them, it reads "Y", and the
others switch to "".
Don Codling
WP 12.0.0.602
DP 2.6x
Windows XP home, SP2
512 MBytes RAM
Michael Iannantuoni wrote:
Hi Brian,
I have a sort of solution for radio buttons:
Each of my check boxes are U1 fields.
To their right is a label field which has a "]" & the response
Question Wording and to the right of that a GZ field which is 1
if the U1 is "X" otherwise 0. Another field sums the GZ's to
keep a tally of how many boxes have been checked.
To the left of the U1 fields is a conditional A1 field which is
either ASCII 249 or "[".
If the selection is multiple option, any available boxes can be
checked.
If the option is Lickert, once a box has been checked, the "["
associated with the other boxes turn to ASCII 249 so no further
entry is possible.
If the user changes their mind, they must uncheck the checked
box which then changes all the other conditional A1 fields back
to "[" thus allowing any to be selected again.
OK, not quite Radio Buttons but only one check box is allowed
as per Lickert.
What do you think?
Michael
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
