Saved vs. SQL Query (1 Viewer)

[georget]

I read that you can improve performance by using a saved Query instead of a sql Query.

Rookie Question...how do I make a Query I created using the Wizard a Saved Query?

My problem....
When my table has 7000 and I use a Query to bring it in the form, the speed of going to the next record is less than a second.

I added 80,000 records and it now takes about 4 seconds to go to each record.

Even when I filter the records to less than 2000 records, it responds like it's searching through 87,000 records.

If "saved query" is the right term. How do I make my query a "saved query"?

 

[georget]

I figured it out.

1) I changed my orginal table name from "data" to "all records"
2) I created a "Make-Table" Query that filters to the table "data"

performance problem solved. hope this helps others.

 

[georget]

My fix has it's problems with multiusers.

 

[DBL]

If you make a query using the wizard it's probably a saved query already. If you create a query and go to File, Save As, give the query a name and it appears under the query objects it's saved. When creating forms and reports you can base them on a query that you don't need to save, it's specific to that form/report.

If you have your database split and are using it in a multi-user environment you will see a loss of performance. However, if the computers are up to the job, it should be too bad.

 

[Pat Hartman]

You will get better help from the members if you don't post the same/similar question multiple times. Continue an existing thread if you have follow on questions:

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=32029