Save data entered into a form

Hi, I am new to access 2003 and have been training myself. I have created a
form based on 2 tables. I have both bound and unbound boxes within the form.
I have a search command button which allows the user to quickly search
through the records to find the correct record and allows data entry into
each text box but when i save the form, all the data entered into the form
is lost and the form opens at the first record again. I have tried to apply a
filter which works, but I still cannot save the data entered into the text
box fields.
I am sure it is a simple expression i need to use, but am still very new to
the expression building process. Any information you may be able to provide
would be greatly appreciated.

--
Lyndy

On Sun, 14 Feb 2010 15:15:01 -0800, Lyndy
wrote:

Hi, I am new to access 2003 and have been training myself. I have created a
form based on 2 tables. I have both bound and unbound boxes within the form.
I have a search command button which allows the user to quickly search
through the records to find the correct record and allows data entry into
each text box but when i save the form, all the data entered into the form
is lost and the form opens at the first record again. I have tried to apply a
filter which works, but I still cannot save the data entered into the text
box fields.
I am sure it is a simple expression i need to use, but am still very new to
the expression building process. Any information you may be able to provide
would be greatly appreciated.

Have you verified that the underlying table is not getting data? If the data
is in the table but not visible in the Form, you may have set the form's Data
Entry property to Yes - this will let you enter new records but will not show
you existing ones.

If that's not it... What is the Form's Recordsource property? Post the SQL
view. And what are the Control Sources of the textboxes which are losing data?


--

John W. Vinson [MVP]

--
Lyndy


"John W. Vinson" wrote:

On Sun, 14 Feb 2010 15:15:01 -0800, Lyndy
wrote:

Hi, I am new to access 2003 and have been training myself. I have created a
form based on 2 tables. I have both bound and unbound boxes within the form.
I have a search command button which allows the user to quickly search
through the records to find the correct record and allows data entry into
each text box but when i save the form, all the data entered into the form
is lost and the form opens at the first record again. I have tried to apply a
filter which works, but I still cannot save the data entered into the text
box fields.
I am sure it is a simple expression i need to use, but am still very new to
the expression building process. Any information you may be able to provide
would be greatly appreciated.

Have you verified that the underlying table is not getting data? If the data
is in the table but not visible in the Form, you may have set the form's Data
Entry property to Yes - this will let you enter new records but will not show
you existing ones.

If that's not it... What is the Form's Recordsource property? Post the SQL
view. And what are the Control Sources of the textboxes which are losing data?


--

John W. Vinson [MVP]
.
Hi John,
Thanks for your response, i feel i may have not explained things well.
I work for a manufacturer and am setting up a system whereby data can be
entered into the form by different departments. Each department will need to
save their data into the form before it moves on to the next department.
Hence the text box control handles.
The form does retrieve data from the tables well, but wont save the data
imputed as a new form. The table (I hope) will be updated automatically as
the data for the exisiting records are entered. I have run queries off this
table and it works well, its the forms Im having trouble with.

Post the SQL... if you're basing your form on a query that is based on 2
tables, it's possible that it's not an updatable. The only way for anyone to
tell is for you to post the SQL...
Open your form in design view, and post the RecordSource for your form....

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/201002/1

On Sun, 14 Feb 2010 18:44:01 -0800, Lyndy
wrote:

Thanks for your response, i feel i may have not explained things well.
I work for a manufacturer and am setting up a system whereby data can be
entered into the form by different departments. Each department will need to
save their data into the form before it moves on to the next department.
Hence the text box control handles.
The form does retrieve data from the tables well, but wont save the data
imputed as a new form. The table (I hope) will be updated automatically as
the data for the exisiting records are entered. I have run queries off this
table and it works well, its the forms Im having trouble with.

Well, it would seem that I haven't explained things well either!

*MOST* Access applications involve bound forms: the form's Recordsource is a
table or (more often) a Query; multitable forms will typically use a bound
form with bound subforms. Entering data into the form directly stores that
data in the table. You can use validation rules in the table, and/or code on
the form to ensure that all departments' data get entered in the proper
sequence.

Your approach can certainly be made to work, but it's a lot more laborious,
since you must provide code to do every little thing that Access does for you
automatically with bound forms. If you've demonstrated to your own
satisfaction that bound forms are unable to meet your needs, then you're stuck
- but I'm guessing that you've leapt directly to unbound forms with
programming to move the data. Am I mistaken?
--

John W. Vinson [MVP]

--
Lyndy


"John W. Vinson" wrote:

On Sun, 14 Feb 2010 18:44:01 -0800, Lyndy
wrote:

Thanks for your response, i feel i may have not explained things well.
I work for a manufacturer and am setting up a system whereby data can be
entered into the form by different departments. Each department will need to
save their data into the form before it moves on to the next department.
Hence the text box control handles.
The form does retrieve data from the tables well, but wont save the data
imputed as a new form. The table (I hope) will be updated automatically as
the data for the exisiting records are entered. I have run queries off this
table and it works well, its the forms Im having trouble with.

Well, it would seem that I haven't explained things well either!

*MOST* Access applications involve bound forms: the form's Recordsource is a
table or (more often) a Query; multitable forms will typically use a bound
form with bound subforms. Entering data into the form directly stores that
data in the table. You can use validation rules in the table, and/or code on
the form to ensure that all departments' data get entered in the proper
sequence.

Your approach can certainly be made to work, but it's a lot more laborious,
since you must provide code to do every little thing that Access does for you
automatically with bound forms. If you've demonstrated to your own
satisfaction that bound forms are unable to meet your needs, then you're stuck
- but I'm guessing that you've leapt directly to unbound forms with
programming to move the data. Am I mistaken?
--

John W. Vinson [MVP]
.Hi John,
Sorry for the delay was out of office.
Yes I did jump straight into the programming as you said and as I am not
very understanding of the systm have encountered all these problems. My
form's RecordSource is as follows:

Products - Transparencies

which is the name of my main table. the second table is an employees list
table.
There are NO data record sources entered into the un bound handles and I now
fear this is where the error is occuring. Do I need to set up another table
which will carry the information entered? I was trying to cut down on the
number of table requirements!

Hello John,
I have just changed the form data record source to run on a query rather
than the table and it now works great!!! Many thanks for your assistance and
patience with a novice like myself.


--
Lyndy


"Lyndy" wrote:


--
Lyndy


"John W. Vinson" wrote:

On Sun, 14 Feb 2010 18:44:01 -0800, Lyndy
wrote:

Thanks for your response, i feel i may have not explained things well.
I work for a manufacturer and am setting up a system whereby data can be
entered into the form by different departments. Each department will need to
save their data into the form before it moves on to the next department.
Hence the text box control handles.
The form does retrieve data from the tables well, but wont save the data
imputed as a new form. The table (I hope) will be updated automatically as
the data for the exisiting records are entered. I have run queries off this
table and it works well, its the forms Im having trouble with.

Well, it would seem that I haven't explained things well either!

*MOST* Access applications involve bound forms: the form's Recordsource is a
table or (more often) a Query; multitable forms will typically use a bound
form with bound subforms. Entering data into the form directly stores that
data in the table. You can use validation rules in the table, and/or code on
the form to ensure that all departments' data get entered in the proper
sequence.

Your approach can certainly be made to work, but it's a lot more laborious,
since you must provide code to do every little thing that Access does for you
automatically with bound forms. If you've demonstrated to your own
satisfaction that bound forms are unable to meet your needs, then you're stuck
- but I'm guessing that you've leapt directly to unbound forms with
programming to move the data. Am I mistaken?
--

John W. Vinson [MVP]
.Hi John,
Sorry for the delay was out of office.
Yes I did jump straight into the programming as you said and as I am not
very understanding of the systm have encountered all these problems. My
form's RecordSource is as follows:

Products - Transparencies

which is the name of my main table. the second table is an employees list
table.
There are NO data record sources entered into the un bound handles and I now
fear this is where the error is occuring. Do I need to set up another table
which will carry the information entered? I was trying to cut down on the
number of table requirements!