Brad Marks
BradM at blackforestltd.com
Fri Jun 21 15:27:08 CDT 2013
All, I have run into a strange error that I have not seen before. We have an Access 2007 Reporting/Inquiry application that has about 50 reports. Many of the reports have "dynamic" filters which enable our users to filter on a specific order, part, customer, date, sales rep, etc. This is accomplished via buttons on the reports (the reports are viewed in "Report View"). Each button opens up a unique "filter form" which collects the filter info from the user and then "sets" the report's filter and turns the filter on with VBA code that looks like this. This approach has worked nicely for over 3 years. Reports.Report100.Filter = str_Where_Condition Reports.Report100.FilterOn = True Recently, the underlying query for one of our reports was enhanced to obtain more data from additional tables. The underlying query works nicely when run in stand-alone mode. The problem is that we are now receiving a "3219" error when we try to set the report filter. This report and its filters were working fine before we added the new fields to the query. I am puzzled. If the query works nicely when it is run stand-alone, I can't understand why setting the report filter would be a problem. No other changes have been made. Perhaps I am missing something. Has anyone else ever run into this situation? Thanks, Brad