Craig Ringer wrote:
If I'm wrong about any of this (which is not unlikely, really) then if
anyone else is lucky enough to be using Access with PostgreSQL and
knows of a better solution or workaround, please feel free to correct me.
We have been working with the combination of a PostgreSQL
Hi all
I've been forced into a project that uses MS Access with PostgreSQL.
This message is intended as a bit of a warning to others who actually
have a choice about it, as there are some issues you may not be aware of
that might sway your decision to use Access in a new project instead of
Craig Ringer wrote:
Hi all
I've been forced into a project that uses MS Access with PostgreSQL.
[snip]
The big issue is with Access's linked table support via ODBC (at least
as of Access 2007). Unlike tools like Hibernate, which are capable of
executing filters, queries across multiple
On Tue, Nov 18, 2008 at 1:10 AM, Craig Ringer
[EMAIL PROTECTED] wrote:
I've been forced into a project that uses MS Access with PostgreSQL.
This message is intended as a bit of a warning to others who actually
have a choice about it, as there are some issues you may not be aware of
that might
Right, passthrough queries is the answer. I once had to build an Access
front end to a very large Oracle database for a client. As you discovered,
directAccess queries can be extermely slow and large. With a passthrough,
all the real work is done on the host database and just the result you want
