Dave Page wrote:

-----Original Message-----

From: Hiroshi Saito [mailto:z-saito ( at ) guitar ( dot ) ocn ( dot ) ne ( dot ) jp] Sent: 10 October 2006 17:19

To: Dave Page; Hiroshi Inoue
Cc: pgsql-odbc ( at ) postgresql ( dot ) org
Subject: Re: [ODBC] New release of psqODBC?

From: Dave Page I've never saw a reply to this question - can you comment please?

Hi Dave.

As for me, tests of 08.02.0102 of the present version is not completed yet.

1.) *nix build for iODBC and unixODBC
2.) *nix build 64bit mode.
3.) MS build for VS2005.
4.) MS build 64bit mode.
5.) MSDTC...

Someone can help them. However, it was not necessarily decided that they would be the specifications still opened wide. Inoue-san has included them and correcting the some bugs. It seems that it becomes the Version 08.02.0103 edition.

Well, we should really gather some of the bug fixes from 08.02.0100 into
an 08.02.0200 release ready for inclusion with pgInstaller. We can
always add further improvements in later versions.

However, Inoue-san is very busy now....

>Sorry for the late answer.
>Unfortunately I can't solve the problems reported by Avery or Andrus yet.
>Anyway I would commit the changes in a day or 2.

>regards,
>Hiroshi Inoue

Don't wait for me, the empty date issue is about as resolved as it will get.  I've dug a little deeper into
ODBC and it seems that ODBC has no concept of "empty dates", so there really isn't a way to get the
driver to represent NULLs as empties when going PostgreSQL->ODBC->FoxPro.  However, converting
empties to NULL is a very practical approach and will be useful to several people. At least it works for
FoxPro->ODBC->PostgreSQL, and that solves all kinds of problems right there.  I would be so bold as
to even suggest that it become a default behavior in the driver, silently converting "empty dates" from
Microsoft data sources into NULL; this appears to be the default behavior for MS Access as well,
so I doubt it will cause issues.