Union Queries

[Natalie]

Okay, so if Union Queries are read only, how can I combine my two tables?
I have two forms:
Main Page -has a check box for O&G
Multi-Tenant Page- has a subform that has a check box for O&G

I need all addresses (main form and multi-tenant form addresses) to be
combined if they have a check for O&G wether it is checked on the main form
or on the subform. A union query works great, but then I can only read the
data. Both forms(tables) have the same fields and I need to combine them so I
can make another form that displays any record address that has a check box.

 

[Golfinray]

Save your union query with another name. Open the new query, turn iit into a
make-table query and make a new table. Now you have an editable table.

 

[Natalie]

If I save it into a table and then make a form from this table will it update
automatically if any of the tables that are linked to the query change?

Also, I do not know how to make a table query from a union query. I can do
it if it is a regular query, but I cannot do if it is a regular query.

 

[Golfinray]

No, you will need to build a query from the new table and then link it to
your other queries or use an update query.

 

[Beetle]

--
_________

Sean Bailey

If I save it into a table and then make a form from this table will it update
automatically if any of the tables that are linked to the query change?

Also, I do not know how to make a table query from a union query. I can do
it if it is a regular query, but I cannot do if it is a regular query.

 

[Beetle]

STOP!

I might be missing something, but from what you describe it sounds
like you already have two different address tables with the same fields. Now
you're going to make a third table, again with the same fields, just because
you are trying to create something updateable?

Sounds like you are making a bad situation worse. What is the reason you
have two different address tables in the first place? It could be that you
just
need to combine the addresses into one table with, perhaps, an extra field
to indicate the different types of addresses. This is only a guess, since I
know nothing about your application, but having two tables with the same
fields would indicate a basic design flaw. You should correct the design
flaw rather than trying to come up with convoluted ways to get around it.

If I have misunderstood your structure post back.