Hello there! I'm Still pretty new to access only been using it for a
couple of days.

If a record has been partially filled out or even completly filled out
and then the form is closed or the user clicks to view an alternative
record i do not want the values they had typed into that record to be
saved.

I only want the valuse to be saved if the user clicks my save button on
my page.

On my form i have set the control source of each of my textboxes to the
relavent colmn in the table but i dont want these to update the table
untill save is selected.

Is this possible? If not could i do an if statment which said something
like..

If any of the textboxes have not been filled out.
Delete this record altogether

If a record has been partially filled out or even completly filled out and then the form is closed or the user clicks to view an alternative record i do not want the values they had typed into that record to be saved.

I only want the valuse to be saved if the user clicks my save button on my page.

[snip]

I don't understand why you would want to do such a thing, but use an unbound
form if this is the behavior you want.

<si************@gmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

Hello there! I'm Still pretty new to access only been using it for a couple of days.

If a record has been partially filled out or even completly filled out and then the form is closed or the user clicks to view an alternative record i do not want the values they had typed into that record to be saved.

I only want the valuse to be saved if the user clicks my save button on my page.

On my form i have set the control source of each of my textboxes to the relavent colmn in the table but i dont want these to update the table untill save is selected.

Is this possible? If not could i do an if statment which said something like..

If any of the textboxes have not been filled out. Delete this record altogether

Many thanks in advance

Rather than focussing on the front-end coding, you should be looking at the
back-end table design. That is, if you do not allow null values or
zero-length strings in the field then you cannot save the record unless you
have filled in the required fields. This is a much more robust way to
prevent 'blanks' than any forms/coding you might come up with.

I want to do this beacause If you only fill out just one text box you
can click go to next record. so someone could create hundreds of
records without fully completing any of them. And i dont want to set
each field to be compulsory because once you click in a textbox you
have to complete it or you cant navigate to anyother part of the form.

I want to do this beacause If you only fill out just one text box you can click go to next record. so someone could create hundreds of records without fully completing any of them. And i dont want to set each field to be compulsory because once you click in a textbox you have to complete it or you cant navigate to anyother part of the form.

Then design your tables with proper required fields and validation rules.
You do not have to adopt a "thin client" interface to achieve proper data
integrity. In addition you can do all sorts of validation in the
BeforeUpdate event of the form and disallow the save in that event if there
is anything about the record you don't like.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

My problem with that are that people who are going to use this database dont like computers.

I want it be as error free as possible. A record that has only partially stored info would confuse people.

But it would be better to have the application indicate what is wrong with
the record rather than just silently discarding it wouldn't it? Your users
will complain that "Your database is broken. I type stuff in and then when
I go back to look for it again it is not there."
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com