Re: Access as a front-end or another query builder

Ellen,

I use Access as my front end, and had the same problem.  In the end I
ended up using pass-thru queries that I created on the fly with a little
VBA.  I still use the query builder in Access to get all of my joins
right (it's so much easier to see it visually when there are a lot of
joins).  I bring the SQL that Access generates into Notepad and hand
massage it until I've got it just right.  After I've got the SQL the way
I want it, I use that string of SQL in VBA and generate my queries on
the fly, changing each of the criteria that needs to be changed each
time I generate the query.  Check out:
http://www.utteraccess.com/forums/showflat.php?Cat=&Board=82&Number=5141
04&Forum=,,All_Forums,,&Words=&Searchpage=1&Limit=25&Main=510514&Search=
true&where=&Name=57586&daterange=&newerval=&newertype=&olderval=&olderty
pe=#Post514104&bodyprev=

Mike

-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Ellen Cyran
Sent: Thursday, February 23, 2006 11:18 AM
To: pgsql-odbc@postgresql.org
Subject: [ODBC] Access as a front-end or another query builder

I've tried the many suggestions about making Access as a front-end to
postgreSQL faster, i.e. turned the ODBC trace off, set Declare/Fetch On,

used the commlog, but it still is about 10 times slower than running the

queries in pgadmin.  The Access pass-thru queries kind of defeat the
purpose of having a query builder since there isn't any design view with

them. Is there an FAQ on setting up Access as a front-end or just steps
that are known to provide reasonable performance?

Are there any good free query builders out there?

Ellen


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq