Queries versus tables

[mark]

Hi:
I have a huge database project i have to do in Access.
However...my system is probably going to have trouble
handling the processing and memory requirements.

What's faster....if I just use queries i need to create a
few intermediate queries first. or should I instead create
a table and base the final query off of the table.

The real question is...how efficient are queries versus
tables.

If I have too many tables...i'll run out of memory. but if
i have too many queries i'm worried it'll take too long to
calculate.

What is your opinion?

 

[RobFMS]

Mark

Some other information that might be helpful:

1. Will this run stand-alone or on a network?
2. Do you have a front-end/back-end database senario or is their just 1
database?
3. What kind of network are you using, if any?
4. What version of Access are you using?

--

Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Problems with your database? Need to upgrade your application?
Contact the FMS Professional Solutions Group: www.fmsinc.com/consulting

Need a Book Recommendation?
www.fmsinc.com/toplevel/books.htm

Need software tools for Access, VB or .NET?
http://www.fmsinc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

[mark]

this database is 99% for making calculations (not much
else)...and storing the results....thus it is not on a
network, there is no front end, and i have access 97.

what do u think of SQL server?

thanx

Mark

 

[Joe Fallon]

I mostly use stacked queries.

The only exceptions are:
1. I need an updateable result set. I toss the query results into a temp
Table and base the update form off the table.
2. Downloading data from an AS/400 - download once to a temp table and base
dozens of reports off the local table. Pay the penalty once at the start
instead of dozens of times (once for each report.)

So - use stacked queries (intermediate results...) unless the exceptions
apply.