Is it possible to join a table to a query that is not updateable?

[Tom]

If so, how?

 

[Granny Spitz via AccessMonster.com]

If so, how?

The answer is here, hon:
http://www.accessmonster.com/Uwe/Fo...ink-a-table-to-a-query-that-is-not-updateable

 

[Guest]

Tom,

Don't post the same question twice. Instead, find the original thread that
you started. You'll see that Granny Spitz answered your question:

http://www.microsoft.com/office/com...cess&mid=9ec4f6aa-7ed4-4231-820d-f7eeb71da724

Also, use that big white area to write your question. When you try to put
too much into the subject, it is cut off, and cannot be viewed easily.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Tom]

The question has not really been answered.

I have also been reading the
docs regarding updateable queries, and the answer
to this question is still unclear to me.

It does say the following in help, but I am not clear
on what inconsistent updates means exactly, and does
this mean you can't join a table to the query?

Though you can't update the data in the query directly, you can update the data in a form based on the query if the form's
RecordsetType property is set to Dynaset (Inconsistent Updates).

 

[Guest]

Ah, I see. The first time you asked if it was possible to link a table to a
query, and Granny did indeed answer that question. For this thread, you
changed one word in the subject, from link to join. So, my question back to
you is did you try to do this? If so, what did or did not happen?

I'm still not sure what exactly the problem is that you are facing. Perhaps
this page will be helpful to you:

Why is my query read-only?
http://allenbrowne.com/ser-61.html


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Rick Brandt]

If so, how?

What do you mean by "join"? If you mean "Can I build a query and use a table
and a non-updateable query as inputs with a join between them?" then you
certainly can do that.

I suspect you are not doing an adequate job of asking your question.

 

[Tom]

What do you mean by "join"? If you mean "Can I build a query and use a table
and a non-updateable query as inputs with a join between them?" then you
certainly can do that.

I suspect you are not doing an adequate job of asking your question.

I asked this question earlier which explains my
problem better in another thread, but it was not answered.

Let us say that there is a table such as

1 a
2 c

and then another complex query to which records
cannot be added such as

a |calculated value|
b |calculated value|
c |calculated value|
d |calculated value|


Is it possible to join this table and query in a manner
Such that further records can be added to it?

For example I want a query that joins the above table
and query where one can add record

3 d

to the table.

 

[Rick Brandt]

I asked this question earlier which explains my
problem better in another thread, but it was not answered.

Let us say that there is a table such as

1 a
2 c

and then another complex query to which records
cannot be added such as

a |calculated value|
b |calculated value|
c |calculated value|
d |calculated value|


Is it possible to join this table and query in a manner
Such that further records can be added to it?

For example I want a query that joins the above table
and query where one can add record

3 d

to the table.

The rules for when a multi-input query is editable are not easy to predict.
I suspect that you would have a hard time getting a query like that to allow
edits. However; since all edits are best done with a form then you can
simply bind a form to the table you need to do inserts on and use any number
of lookup mechanisms to display the related data from your other query.
DLookup() or a subform would be two such mechanisms that would work.

 

[David W. Fenton]

The rules for when a multi-input query is editable are not easy to
predict. I suspect that you would have a hard time getting a query
like that to allow edits. However; since all edits are best done
with a form then you can simply bind a form to the table you need
to do inserts on and use any number of lookup mechanisms to
display the related data from your other query. DLookup() or a
subform would be two such mechanisms that would work.

It's always worth it to try the Jet-specific DISTINCTROW predicate,
as in SELECT DISTINCTROW..., because that can often make things
editable which otherwise are not.