T
Tofudisan
I've searched the forum archives and haven't found the same scenario
I'm in. There's a few similar problems but the proposals in those
didn't work for me so I'm posting a new plea for help.
I have a small 3-user database. It's a Access 2000 front-end with a
SQL back-end. The application has a main form that handles 99.99% of
the user interaction (the rest is look-up list editing forms). There
are no sub-forms or tabs or anything else remotely complicated about
the form.
Anyway the problem I've run into is that whenever a record is updated
and then saved the form jumps to the first record in the database
instead of "staying put" on the record that was edited.
How do I get it to stop this behavior? I want the user to be able to
edit and update a record and stay on THAT record.
I'm in. There's a few similar problems but the proposals in those
didn't work for me so I'm posting a new plea for help.
I have a small 3-user database. It's a Access 2000 front-end with a
SQL back-end. The application has a main form that handles 99.99% of
the user interaction (the rest is look-up list editing forms). There
are no sub-forms or tabs or anything else remotely complicated about
the form.
Anyway the problem I've run into is that whenever a record is updated
and then saved the form jumps to the first record in the database
instead of "staying put" on the record that was edited.
How do I get it to stop this behavior? I want the user to be able to
edit and update a record and stay on THAT record.