Re: postgres/odbc/ms access versions

On 11/16/2015 09:15 AM, Garnham, Sam (FN) @ NSS - ASA wrote:
> Hello,
>
> We were using these versions:
>
> -PostgreSQL 9.1.1 (Sept 2011)
>
> -PostgreSQL ODBC Driver 09.00.0310 (July 2011)
>
> -MS Access 2010
>
> -Windows 7 Professional 32-bit
>
> We have upgraded to this:
>
> -PostgreSQL 9.1.19 (Latest 9.1 - Oct 2015)
>
> Is it safe/recommended to also upgrade to this?
>
> -PostgreSQL ODBC Driver 09.03.0400 (Latest - Oct 2014)
>
> Or maybe this?
>
> -PostgreSQL ODBC Driver 09.01.0200 (Latest 09.01 – Aug 2012)
>
> (If it makes any difference, we are more concerned with reliability than
> with performance)

 From here:

http://www.postgresql.org/ftp/odbc/versions/

" Unless you have have a specific reason not to do so, you should always
download the latest version."

To determine whether there is specific reason see link below.

>
> Are the version numbers related - Postgres 9.1 / ODBC driver 09.01?
>
> Is there any documentation available on the compatibility of different
> versions of these components?

https://odbc.postgresql.org/docs/release.html

>
> Kind Regards,
>
> *Sam Garnham | Principal Engineer*
>
> *L-3 Communications ASA Ltd//*
>
> Rusint House, Harvest Crescent, Fleet, Hampshire, GU51 2QS, England
>
> Office No: +44 (0) 1252 775722
>
> www.L-3ASA.com <http://www.l-3asa.com/>
>
> *Please consider the environment before printing this email* -
> ------------------------------------------------------------------------
>
> This communication is confidential to the intended recipient (s). If you
> are not that person you are not permitted to make use of the information
> and you are requested to notify the sender immediately of its receipt
> and then destroy the copy in your possession. Any views or opinions
> expressed are those of the originator and may not represent those of L-3
> Communication ASA Ltd.
>
> Sent from L-3 Communications ASA Ltd. Registered in England and Wales
> Company No. 1730717. Registered Office: 100 New Bridge Street, London,
> EC4V 6JA
>


--
Adrian Klaver
adrian.klaver@aklaver.com