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.
David P. Lurie
pgsql-odbc by date
|Next:||From: Philippe Lang||Date: 2004-08-05 16:18:29|
|Subject: Re: Filter equivalent for Access bound form|
|Previous:||From: postgresql||Date: 2004-08-04 18:22:00|
|Subject: SSL as unpriviledged user|