Update records by command button only

[Guest]

I have taken the navigation buttons from the form and would like to move all
the submit\update\add new record to a command button.

The command button is fine, it works, but the form still moves onto a new
record using the enter key. I would rather the records stay put until it is
told to update and bring up a new record by the button click.

Is there anyway that I can turn off these actions??

I hope that this is clear enough.

 

[Guest]

Maybe there is a better way but one method would be to use an unbound form
and use the "save" button to SetValue to the table(s)

As soon as you enter data into a bound control the value will be saved into
the table field so you may have a problem. There are a few mthods but the
unbound forms seems the simplist

Hope this helps

 

[Guest]

It sounds like the Cycle property of the form is set to All Records. Change
it to Current Record.
That will not totally resolve the problem because if the user navigates away
from the current record either through navigation buttons or closing the
form, you have to deal with it.

 

[Albert D. Kallal]

The enter key does not normally bring up a new record.

Normally, hitting enter key will move to the next field. and, so does
hitting the tab key.

If you on the last control of the form, then hitting tab, or enter MAY move
to the next record if thats how you have your form setup.

You can set the forms 'cycle' properity in the "other" tab to curretn record
to disapble this.

In fact, in these cases, I also set the forms "allow" additions = false, as
then a accident page down, or even moving the mouse wheel will NOT blank out
all fields...save..and move to the next record.

Do remember, if you change the forms "cycle" property to current record,
then data entry people will not be able to us the keyboard, and will have to
take extra time out of their day to use your save button, and THEN hit
another button to move to the next new record. So, you are taking away
productive time from your users that could be used to feed the poor, or help
make the world a better place......

 

[Guest]

Great. I thought it'd be that simple.

Thats fine, the point is that the user only needs to enter the one record in
the first place. The problem was that when this moved to a new record it
would appear as though the form had lost your additions, and wouldn;t allow a
new record to be added because the primary key would duplicate. And the save
function will move to the new record by itself if that is needed. In anycase
it is fine for now.