Can't enter data. Why?

I've created 4 tables, linked them together, queried, created forms based on the queries, but am not allowed to actually enter data into the forms based on queries.

What should I look for as the culprit locking data entry out?

Thanks,
Wanda

One, is the query updatable....can you change data if you open the query on
its own? If not, then the form won't let you change data or enter data
either. See these MS Knowledge Base articles for more info about updatable
queries:

ACC2000: Cannot Edit or Update Record on a Form
http://support.microsoft.com/default...71&Product=acc

ACC2000: Status Bar Displays "Recordset Not Updateable" Message When You Try
to Update a Linked Table
http://support.microsoft.com/default...79&Product=acc

INFO: Troubleshooting Errors That May Occur When You Update Data in Queries
and in Forms
http://support.microsoft.com/default...28&Product=acc

ACC: Update Query Based on Totals Query Fails
http://support.microsoft.com/default...42&Product=acc


Also, if the query works ok on its own, then check to see if the "Allow
Edits" and "Allow Additions" properties are set to yes for the form.

--
Ken Snell
MS ACCESS MVP


"Wanda" wrote in message
...
I've created 4 tables, linked them together, queried, created forms based
on the queries, but am not allowed to actually enter data into the forms
based on queries.

What should I look for as the culprit locking data entry out?

Thanks,
Wanda

"Wanda" wrote in message
...
I've created 4 tables, linked them together, queried, created forms based
on the queries, but am not allowed to actually enter data into the forms
based on queries.

What should I look for as the culprit locking data entry out?


Hi
That is normally what happens when you base update forms on queries. Update
forms should be based on the base table. Individual fields on the form then
have listboxes or comboboxes to get the fields from related tables.

HTH
Marc

Sorry, Marc, but using a query as a form's recordsource is usually preferred
over using the table in most cases.

--
Ken Snell
MS ACCESS MVP

"Marc" wrote in message
...

"Wanda" wrote in message
...
I've created 4 tables, linked them together, queried, created forms
based
on the queries, but am not allowed to actually enter data into the forms
based on queries.

What should I look for as the culprit locking data entry out?


Hi
That is normally what happens when you base update forms on queries.
Update
forms should be based on the base table. Individual fields on the form
then
have listboxes or comboboxes to get the fields from related tables.

HTH
Marc

"Ken Snell" wrote in message
...
Sorry, Marc, but using a query as a form's recordsource is usually
preferred
over using the table in most cases.

--
Ken Snell
MS ACCESS MVP


Always interested in knowing exactly why is that?
Ta
Marc

A query gives you the ability to provide order to your records and gives you
the ability to join tables (data) together.

This isn't meant to say that you *never* use a table as the recordsource,
but it's rare that I do that.

--
Ken Snell
MS ACCESS MVP


"Marc" wrote in message
...

"Ken Snell" wrote in message
...
Sorry, Marc, but using a query as a form's recordsource is usually
preferred
over using the table in most cases.

--
Ken Snell
MS ACCESS MVP


Always interested in knowing exactly why is that?
Ta
Marc

snip
A query gives you the ability to provide order to your records and gives
you
the ability to join tables (data) together.

This isn't meant to say that you *never* use a table as the recordsource,
but it's rare that I do that.

Ok, so there's no compelling technical reason. From a recordsource, that is
ordered will do just as well, and not make a nonupdateable recordset, which
is what the question was about.

Thanks
Marc

No, there is not a technical reason for it, but note that using a table
means you cannot update related tables via the form's built-in
functionality. And often, data are being updated/entered in more than one
table at a time.

--
Ken Snell
MS ACCESS MVP

"Marc" wrote in message
...
snip
A query gives you the ability to provide order to your records and gives
you
the ability to join tables (data) together.

This isn't meant to say that you *never* use a table as the
recordsource,
but it's rare that I do that.

Ok, so there's no compelling technical reason. From a recordsource, that
is
ordered will do just as well, and not make a nonupdateable recordset,
which
is what the question was about.

Thanks
Marc