By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,808 Members | 1,477 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,808 IT Pros & Developers. It's quick & easy.

How to se filter or recordsource

P: 4
I populate many of my MS Access forms with only one record from a single table. Is it faster/better to use a SQL statement (with appropriate WHERE statement) applied directly to the recordsource or point the recordsource to the appropriate table and set the filter each time the form opens? Does the version (2003 vs. 2007) or the use of a SQL back-end make a difference?
May 13 '10 #1

✓ answered by NeoPa

I don't believe there is ever much of a performance difference between the two approaches. I'd always recommend the full table with a filter though, for flexibility as well as ease of maintenance.

Welcome to Bytes!

Share this Question
Share on Google+
6 Replies


NeoPa
Expert Mod 15k+
P: 31,489
I don't believe there is ever much of a performance difference between the two approaches. I'd always recommend the full table with a filter though, for flexibility as well as ease of maintenance.

Welcome to Bytes!
May 14 '10 #2

P: 4
Thanks; I was under the impression that the recordsource approach would be processed by the server and the filter would be processed by the client? Hence, the former approach would limit network traffic??
May 14 '10 #3

Jim Doherty
Expert 100+
P: 897
@johnhawk
How many times do we see
"Select * from the largest table in the universe" across the network and filter it when it gets to the client
as opposed to
"Select only the columns you need and the number of rows that you can define as needing from the largest table in the universe where my criteria equals an indexed column"

For the most part with small stuff you don't notice much difference :)
May 14 '10 #4

P: 4
@johnhawk
Thanks for the quick reply.
May 14 '10 #5

NeoPa
Expert Mod 15k+
P: 31,489
johnhawk: Thanks; I was under the impression that the recordsource approach would be processed by the server and the filter would be processed by the client? Hence, the former approach would limit network traffic??
Just to be clear - that is not what is going on here with filtered forms. It's all handled by the SQL engine.
May 14 '10 #6

P: 4
@NeoPa
Thanks, again. Makes sense.
May 14 '10 #7

Post your reply

Sign in to post your reply or Sign up for a free account.