Hello,
Using the filter property of a bound form is not a problem I think, at least with Access 2000. The filtering is done
server-side,and only the necessary data is fetched on the client. I don't think this is a performance penalty.
But with Access 2003, I agree I have problems too. For an unknown reason, filtering is apprently done client-side,
don'task me why...
I have to check that...
Philippe Lang
-----Message d'origine-----
De : pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] De la part de David P. Lurie
Envoyé : jeudi, 5. août 2004 17:47
À : pgsql-odbc@postgresql.org
Objet : [ODBC] Filter equivalent for Access bound form
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.recordsourceWHERE 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
workfor 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
apassthrough query?
Would need a unique view name for multi-user reasons, perhaps including part of a timestamp string or sequence. The
originalview's insert, update and delete rules should still have valid syntax except for the new view name, as only the
WHEREclause 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
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
