M$ Access as fronted for pg with pgsqlodbc

This message is in MIME format.

--=_1avbtmrhd334
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Description: Plaintext Version of Message
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



Hi,

We are developing an application on ms access that will become the =20
frontend for psotgresql, the application will be used by more than 40 =20
workstations, the apps is for registration of students.

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

This is our first time to use posgresql and be implemented as =20
school wide database backend.

thank you very much!
oca


--=_1avbtmrhd334
Content-Type: text/html;
charset=ISO-8859-1
Content-Description: HTML Version of Message
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

We are developing an application on ms access that will become =
the
frontend for psotgresql, the application will be used by more than 40
workstations, the apps is for registration of students.

We are very mu=
ch
concerned about the speed, any tips to avoid while developing application in=
=A0M$
Access as front end?

This is our first time to use posgresql and be
implemented as school wide database backend.

thank you very much! />oca

Re: M$ Access as fronted for pg with pgsqlodbc

On Mon, Sep 1, 2008 at 6:59 PM, 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

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: M$ Access as fronted for pg with pgsqlodbc

This message is in MIME format.

--=_1odfo89jlme8
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Description: Plaintext Version of Message
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



Thank you! ----- Message from richard.broersma@gmail.com ---------
=A0 =A0 Date: Mon, 1 Sep 2008 21:06:59 -0700
=A0 =A0 From: Richard Broersma
Reply-To: Richard Broersma
Subject: Re: [ODBC] M$ Access as fronted for pg with pgsqlodbc
=A0 =A0 =A0 To: oca@mvc.edu.ph
=A0 =A0 =A0 Cc: pgsql-odbc

> On Mon, Sep 1, 2008 at 6:59 PM,=A0 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.=A0 the MS Jet engine
> sees null booleans as false.=A0 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
>
> --
> Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-odbc
>

----- End message from richard.broersma@gmail.com -----




--=_1odfo89jlme8
Content-Type: text/html;
charset=ISO-8859-1
Content-Description: HTML Version of Message
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Thank you!