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,

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to rbase-l@rbase.com

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to rbase-l@rbase.com
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: Send a plain text email to rbase-l@rbase.com
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to rbase-l@rbase.com
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, place any text to search for.
================================================


Reply via email to