Filter equivalent for Access bound form
От | David P. Lurie |
---|---|
Тема | Filter equivalent for Access bound form |
Дата | |
Msg-id | cetkpv$qll$1@sea.gmane.org обсуждение исходный текст |
Ответы |
Re: Filter equivalent for Access bound form
|
Список | pgsql-odbc |
Access 2003 pg 7.4.3 What is the recommended approach to get the equivalent of a filter for an Access bound form? The filter property of a bound form seems to be the equivalent of an Access client-side query of SELECT * FROM form.recordsource WHERE form.filter. That would have a performance penalty. I change the SQL of pass-through queries dynamically at runtime to use as record sources for reports. That wouldn't work for forms, as not updatable. Is the best approach to use an updatable view as the record source, then change the view definition at runtime as with a passthrough query? Would need a unique view name for multi-user reasons, perhaps including part of a timestamp string or sequence. The original view's insert, update and delete rules should still have valid syntax except for the new view name, as only the WHERE clause and view name are changed. The rules could be updated with VBA code at the same time as the view change. Thanks, David P. Lurie
В списке pgsql-odbc по дате отправления: