Query vs. Table

  • Thread starter Thread starter Guest
  • Start date Start date
No. Not by an experienced Access user.

A query is a device used to pull data from a table and normally filters it
in some way.

A table is the object where the records are stored. It defines each field
type and size, etc.

While both can be used as the source for reports, forms, and even other
queries, they are not the same.
 
You don't. Why would you want to do that? The query should be pulling data
from a table.

If you are trying to filter the data from a table by putting criteria in the
query, then you can do so and save that query. The query can then be used
to create a report or a form. There would be no need to save it as a table
first.

What are you trying to accomplish?
 
As part of a job interview yesterday, I was asked to create a new table using
a query to pull data from two existing tables. Rather than creating a new
table, I renamed and saved the query. I am trying to gauge wether I fully
completed the task, or if by leaving the new information as a saved query, I
fell short of what was expected.

I appreciate your assistance.
 
Well, you did not technically answer the question. They wanted you to
create a "Make Table" query. But, their request was not necessarily valid.
I would almost never create a new table from two existing table unless I was
trying to "normalize" a bad design.

So, for example, if you have a table listing all "boys" and a table listing
all "girls" it might be better to combine these into a new table of "kids".
To do so, you'd need to add a new "gender" field, then combine the data and
put it in a new table.

If you are working with a properly normalized database, it would be rare
that you'd need to create a new table from two existing tables. The reason
is that you can do pretty much anything with the saved query that you can do
with a table AND... if someone changes data in the tables, the stored query
would reflect those changes. If you create a new table and someone goes
back and needs to modify data, they must now update the existing table AND
your new table. By using the query instead, they would only need to update
the existing table. Those changes would be reflected in your query, and in
any object using that query as it's data source.

Maybe someone else will have some additional comments as to how they think
your answer was taken. I have never been in an interview that asked me to
perform a skill like that.

Hope you get it!!!
 
I worked for a company where I had to create a temporary table from two
existing tables - but that's just it - it was a temporary table. I can see
where you might want to do that in order to have the data stored in a temp
table to access easily while doing things like calculations, other queries,
etc.; however, I also don't see any reason you would want to create a
completely new table from two existing tables unless you are normalizing,
combining, or creating an entirely new database. It would be better just to
create a "Union" table from the two existing tables, if you are going to
need to constantly access data from both tables...

Hope that helps a little...

Coleen
 
Back
Top