At least that confirms I'm not going nuts. I'll pull in an older copy
of the form and see if it works, hopefully I don't need to go back too far.
On 7/25/2011 12:36 PM, [email protected] wrote:
Dave: I've had this happen to me, in both 7.6 and 9.1. Originally
the "exit" pre-defined button would work correctly, asking whether to
save or not. Then I would make some changes to the form and the "exit"
would now simply close the form without saving anything. I cannot
replicate it reliably, and have no idea what changes I made that would
cause it so have never submitted it to RBTI for review. But I'll get
it's happened dozens of time for me. Normally I would go back to a
backup copy of the form, make a few changes, test it from r> promp to
see if the exit works, then continue until I'm able to get all my
changes in there, and the form will always work then. So sorry, no
solution, just that I've had the same thing happen.
Karen
I have some odd behavior in my current project which I've been working
on for some time, so I can't say exactly when it began. However, I'm
running latest build of R:base 9.1 32.
All my edit forms are setup with buttons which issue a pre-defined Exit,
tables set to Auto save changes. If one changes values, hit the
button, you'll get prompted if you'd like to Save the changes.
Now just recently I noticed my client table/edit form will NOT prompt to
save, nor does it save changes if you hit this button, it just exists
without saving anything. I have a DB navigator control on the form
also, the "cancel" option in the navigator becomes "active" when you
make a change, indicating it has sensed a change, and if you hit the
next row button the change IS saved, but NOT if you just exit the form.
If I change the button action to Save and exit, it will save properly,
but this is not the behavior I'd like as I want the confirmation like
all the others.
I've checked all the form settings, unloaded/reloaded the form, etc.
Oddly, another very OLD version of this form dealing with the same table
does work correctly.
Anybody seen such a thing? Any ideas?
Thanks,
-----Original Message-----
From: Dave McCann <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Sun, Jul 24, 2011 9:46 pm
Subject: [RBASE-L] - strange form data saving behavior
I have some odd behavior in my current project which I've been working
on for some time, so I can't say exactly when it began. However, I'm
running latest build of R:base 9.1 32.
All my edit forms are setup with buttons which issue a pre-defined Exit,
tables set to Auto save changes. If one changes values, hit the
button, you'll get prompted if you'd like to Save the changes.
Now just recently I noticed my client table/edit form will NOT prompt to
save, nor does it save changes if you hit this button, it just exists
without saving anything. I have a DB navigator control on the form
also, the "cancel" option in the navigator becomes "active" when you
make a change, indicating it has sensed a change, and if you hit the
next row button the change IS saved, but NOT if you just exit the form.
If I change the button action to Save and exit, it will save properly,
but this is not the behavior I'd like as I want the confirmation like
all the others.
I've checked all the form settings, unloaded/reloaded the form, etc.
Oddly, another very OLD version of this form dealing with the same table
does work correctly.
Anybody seen such a thing? Any ideas?
Thanks,
