Re: psqlODBC 09.06.0400 Released

Hi Robert,

Could you please try the test drivers 9.6.0401 at
http://www.ne.jp/asahi/inocchichichi/entrance/psqlodbc/
<http://www.ne.jp/asahi/inocchichichi/entrance/psqlodbc/>
?

regards,
Hiroshi Inoue

On 2017/07/21 16:36, Inoue, Hiroshi wrote:
> Hi Robert,
>
> On 2017/07/20 23:19, Robert Ball wrote:
>> Hello
>>
>> We are also encountering issues when using psqlODBC 09.06.0400 with
>> MSACCESS 2016, it seems to lose the connection to the database. I can
>> open forms, but get issues with some data not showing, similar to
>> Christian but mine shows "#Name?" rather than "#Deleted" .
>>
>> If I try and look at a table via MSACCESS sometimes I can see the
>> data, other times I get an "ODBC -- call failed" error.
>
> Thanks for the report.
>
>>
>> Even though I have debug enabled I get no log files generated.
>
> Do you turn on the global debug option?
>
> regards,
> Hiroshi Inoue
>>
>> Everything works fine when we use psqlODBC 09.06.0310
>>
>> Regards
>> Robert Ball
>>
>> Manifest
>>
>> Tel: +44 (0)1376 504511 | Main: +44 (0)1376 503500 | Fax: +44 (0)1376
>> 503550
>>
>> Blog: https://blog.manifest.co.uk/ | Web: https://www.manifest.co.uk/
>>
>> 9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL |
>> England
>>
>> ----------------------------------------------------------------------------------------------------------------------------
>>
>>
>> Copyright: This e-mail may contain confidential or legally privileged
>> information. If you are not the named addressee you must not use or
>> disclose such information, instead please report it to
>> admin(at)manifest(dot)co(dot)uk(dot)
>> Legal: Manifest is the trading name of: Manifest Information Services
>> Ltd: Registered in England Number 3401145 & The Manifest Voting
>> Agency Ltd: Registered in England Number 2920820 Registered Office at
>> above address. Please Click Here https://www.manifest.co.uk/legal/
>> for further information.
>>
>> -----Original Message-----
>> From: pgsql-odbc-owner(at)postgresql(dot)org
>> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Christian Ullrich
>> Sent: 20 July 2017 15:08
>> To: pgsql-odbc(at)postgresql(dot)org
>> Subject: Re: [ODBC] psqlODBC 09.06.0400 Released
>>
>> * Hiroshi Saito wrote:
>>
>>> We are pleased to annouce the release of psqlODBC 09.06.0400.
>> Hello,
>>
>> this release changes the behavior of linked tables in MS Access 2016
>> (x86). With 9.6.310, all is well, with .400, for some tables the data
>> looks good, some are entirely filled with "#Deleted".
>>
>> Most interestingly, however, for some tables, exactly 9 out of every
>> 10 rows in datasheet view are "#Deleted". Specifically, there are
>> always nine rows like that, followed by one with valid data. If I
>> change the sort order of any column, I get a screenful of valid rows,
>> except for the selected row; that one stays at "#Deleted".
>>
>> Changing sort order always jumps the view back up to the first row;
>> when I scroll down, everything below the first page is still similar
>> to before; nine rows #Deleted, one row valid, repeat. The pattern
>> resumes at the page edge, i.e. if the window does not show a multiple
>> of 10 rows the valid rows after scrolling down will be different ones
>> than before.
>>
>> I have switched back and forth between .310 and .400 a few times,
>> with reproducible results each time.
>>
>> There is no apparent correlation between .400's behavior for any
>> given table and the content of that table. ISTR that Access likes
>> timestamp columns for identifying rows; none of my tables have any.
>>
>> The behavior is the same with default data source options and with
>> these nondefault options:
>>
>> - "Row Versioning" enabled
>> - "True is -1" enabled
>> - "Bools as Char" disabled
>>
>> In my experience, these settings are necessary for Access to work at
>> all.
>>
>> Screenshot attached.
>>
>> --
>> Christian