• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Working with Server Filters

As you learned in Chapter 19, when you specify a server filter, Access includes the filter in the request it sends to the server. The server selects the rows that meet the criteria in the server filter and sends only the requested data back to Access. Server filters are advantageous because they reduce the size of the recordset, fetching only the data the user needs to see. You can also set the Filter property on a report, but Access doesn’t apply that filter until it has fetched all the unfiltered data from the server. Using a server filter cuts down on the time a server must spend processing the recordset and eliminates the time that Access would otherwise spend applying the filter on your client machine. You can imagine that using a server filter can have a significant impact on the efficiency of your reports, particularly when the underlying tables needed for a report contain hundreds of thousands of rows.

Although server filters are very advantageous, you can use them only when your report has a table or a view as its record source. You can define a server filter for a report that is bound to an in-line function, but Access ignores it. If you try to define a server filter for a report bound to a stored procedure, Access displays a warning message when you try to open the report: “A Server Filter cannot be applied to a stored procedure Record Source. Filter not applied.” Tables and views do not support parameters, so you cannot design a report that uses both parameters and server filters. As you’ll learn later in this chapter, parameters can be just as effective as server filters when you bind your report to a function or stored procedure.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint