Re: M$ Access as fronted for pg with pgsqlodbc - Mailing list pgsql-odbc

From Richard Broersma
Subject Re: M$ Access as fronted for pg with pgsqlodbc
Date
Msg-id 396486430809012106l3d30f52fo462b1f08a21de65c@mail.gmail.com
Whole thread Raw
In response to M$ Access as fronted for pg with pgsqlodbc  (oca@mvc.edu.ph)
Responses Re: M$ Access as fronted for pg with pgsqlodbc  (oca@mvc.edu.ph)
List pgsql-odbc
On Mon, Sep 1, 2008 at 6:59 PM,  <oca@mvc.edu.ph> wrote:


> We are very much concerned about the speed, any tips to avoid while
> developing application in M$ Access as front end?

1) do not use nullable booleans on the pg tables.  the MS Jet engine
sees null booleans as false.  This makes rows with null booleans not
update-able.
2) When ever possible, perform all large joins on the server not in
the MS-Query editor.
3) SELELT * FROM LargeTable; can be slow, so try to include Where
Clauses when ever possible to limit result set;

--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

pgsql-odbc by date:

Previous
From: oca@mvc.edu.ph
Date:
Subject: M$ Access as fronted for pg with pgsqlodbc
Next
From: oca@mvc.edu.ph
Date:
Subject: Re: M$ Access as fronted for pg with pgsqlodbc