Skip site navigation (1) Skip section navigation (2)

efficiency of ODBC, MS-Access, subforms with filter

From: Andreas <maps(dot)on(at)gmx(dot)net>
To: pgsql-odbc(at)postgresql(dot)org
Subject: efficiency of ODBC, MS-Access, subforms with filter
Date: 2006-03-19 04:46:58
Message-ID: 441CE242.4000504@gmx.net (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi,

This question might sound a wee bit off-topic but it isn't really.

I've got some tables with related info.
There is a table of customers and some tables with other stuff like 
adresses, contacts, letters, ...
Up until now all was stored in a shared MS-Access MDB.

I have a form that shows all the stuff per customer.
The contacts and letters and a few other tables are selected into subforms.
This sucks big time with linked tables out of a MDB via network so I 
want to move the backend to PostgreSQL.

Now I try to figure out how I could make my forms as fast as possible.

Subforms can't be based on pass-through-queries in memory so I can 
either have linked PostgreSQL tables that get filtered by the form or 
create dynamically querydef-objects. Those querydefs would get written 
to the mdb-file so I'd lose time again.

Am I to hope that Access tells the odbc-driver the filter crtiterium of 
subforms so that it just fetches the few records that relate to the 
customer shown on the parent-form?
Or would it rather fetch all records in the source table/view and then 
sort the interesting records out locally?



pgsql-odbc by date

Next:From: Bart SamwelDate: 2006-03-19 12:44:28
Subject: Re: Most recent driver aborts transaction after one error
Previous:From: Bart SamwelDate: 2006-03-18 23:29:56
Subject: Re: Most recent driver aborts transaction after one error

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group