Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 4291 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I am adding records to a table by calling a new record request.  the key is not to be created until the user "commits" the record.  I have a "save" button which will call the "commit command" as well as a "cancel" button.  What is happening is that as soon if the user goes to the "next" record, the current record is being added without the user having to tap the "save" button.  I want the ability to stop the user from leaving the current record unless the data is "committed" by using the save button so as all the validity checking can be done or the data is cancelled.  

 

I am sure there is a simple way to accomplish this but I am not sure how.

 

any help would be appreciated.

 

thanks.

Posted

I couldnot understand your problem. Once rew record request is called, a new record will be created and in that record, after filling data in a field when user clicks outside of field or moves to other field, the record will be saved(auto commited). So what is the need of giving a commit button?

This topic is 4291 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.