Why create another table, which holds the results? Instead, pass the results of a query to another query (this is called Nested Queries)
http://www.sql-tutorial.com/sql-nested-queries-sql-tutorial/[
^]
[edit]One of the reasons not to do what you propose is that it won't work at all in a multiuser environment: Who last put the data into the table? Was it you? Or someone half the world away? You don't know, and you can't assume it was you.
If you must put it into a table, then look at Temporary Tables, and do it in a stored procedure.
But by preference, don't do it at all, unless you really have to.[/edit]