Re: New 9.5.0100 does not work properly

On 01/12/2016 12:36 AM, Walter Willmertinger wrote:

Ccing list, so more eyes can see this.

> The "Write Conflict" is independent of the setting "row versioning".
> When I strted it was switched off. I switched to "On", but the same result.

What did you do in between?

In other words did you disconnect/reconnect from the database, log
out/log in, rboot, etc?

I have had issues with ODBC not catching changes to its conf, especially
when there is a live connection.

>
> _Here is an excerpt from mylog:_
>
> /[7.065]conn=000001F55B153090, query='SELECT
> "KundenCode","DatumEreignis","AufnahmeDurchPersonalNr","WeiterAnPersonalNr","Status","Notiz","KdID","Prioritaet","ProgErledigt","update_cs","ZuletztBearbeitetPersonalNr"
> FROM "public"."Notizen" WHERE "KundenCode" = E'1' AND "KdID" = 83'
> [8.455]ParseAndDescribeWithLibpq: plan_name= query=UPDATE
> "public"."Notizen" SET "Notiz"=$1 WHERE "KundenCode" = $2 AND "KdID" =
> $3 AND "DatumEreignis" = $4 AND "AufnahmeDurchPersonalNr" = $5 AND
> "WeiterAnPersonalNr" = $6 AND "Status" = $7 AND "Prioritaet" IS NULL AND
> "ProgErledigt" = $8 AND "update_cs" = $9 AND
> "ZuletztBearbeitetPersonalNr" IS NULL
> [8.456]conn=000001F55B153090, query='BEGIN'
> [8.457]ParseWithLibpq: plan_name= query=UPDATE "public"."Notizen" SET
> "Notiz"=$1 WHERE "KundenCode" = $2 AND "KdID" = $3 AND "DatumEreignis" =
> $4 AND "AufnahmeDurchPersonalNr" = $5 AND "WeiterAnPersonalNr" = $6 AND
> "Status" = $7 AND "Prioritaet" IS NULL AND "ProgErledigt" = $8 AND
> "update_cs" = $9 AND "ZuletztBearbeitetPersonalNr" IS NULL
> [8.460]conn=000001F55B153090, query='UPDATE "public"."Notizen" SET
> "Notiz"=E'Test xxx' WHERE "KundenCode" = E'1' AND "KdID" = 83 AND
> "DatumEreignis" = E'2015-09-30 13:48:13'::timestamp AND
> "AufnahmeDurchPersonalNr" = 80 AND "WeiterAnPersonalNr" = 80 AND
> "Status" = E'E' AND "Prioritaet" IS NULL AND "ProgErledigt" = E'0' AND
> "update_cs" = E'2015-09-30 13:48:15'::timestamp AND
> "ZuletztBearbeitetPersonalNr" IS NULL'
> [8.464]conn=000001F55B153090, query='ROLLBACK'/

On the face of it the above looks alright. I have seen issues such as
you describe with Access and Postgres when using fractional second
timestamps, but the above uses integer seconds.

>
> _Here is my "ODBC.INI":_
> /[ODBC 32 bit Data Sources]/
> /PgSQL_CONSYS=PostgreSQL ANSI(x64) (32 bit)
> /
> /[PgSQL_CONSYS]
> /
> /Driver32=C:\Program Files\psqlODBC\0903\bin\psqlodbc30a.dll/
>
> *But it's Access 2013 64-bit!*

How did you install psqlodbc and from what source?

Also what OS and version are you running on?

I do not fully understand the 32/64 bit thing in Windows, so I will
point you at this:

https://odbc.postgresql.org/faq.html#6.8

>
> _Here my registry settings for this ODBC-Entry:_
>
> /[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\PgSQL_CONSYS]/
> /"Driver"="C:\\Program Files\\psqlODBC\\0903\\bin\\psqlodbc30a.dll"/
> /"CommLog"="1"/
> /"Debug"="0"/
> /"Fetch"="100"/
> /"Optimizer"="0"/
> /"Ksqo"="1"/
> /"UniqueIndex"="1"/
> /"UseDeclareFetch"="0"/
> /"UnknownSizes"="0"/
> /"TextAsLongVarchar"="1"/
> /"UnknownsAsLongVarchar"="0"/
> /"BoolsAsChar"="1"/
> /"Parse"="0"/
> /"CancelAsFreeStmt"="0"/
> /"MaxVarcharSize"="255"/
> /"MaxLongVarcharSize"="8190"/
> /"ExtraSysTablePrefixes"="dd_;"/
> /"Description"="Access 64 Bit"/
> /"Database"="consys"/
> /"Servername"="col"/
> /"Port"="5445"/
> /"Username"="XXXXX"/
> /"UID"="YYYYY"/
> /"Password"="ZZZZZZ"/
> /"ReadOnly"="0"/
> /"ShowOidColumn"="0"/
> /"FakeOidIndex"="0"/
> /"RowVersioning"="0"/
> /"ShowSystemTables"="0"/
> /"Protocol"="7.4-1"/
> /"ConnSettings"=""/
> /"DisallowPremature"="0"/
> /"UpdatableCursors"="0"/
> /"LFConversion"="1"/
> /"TrueIsMinus1"="1"/
> /"BI"="0"/
> /"AB"="0"/
> /"ByteaAsLongVarBinary"="0"/
> /"UseServerSidePrepare"="0"/
> /"LowerCaseIdentifier"="0"/
> /"GssAuthUseGSS"="0"/
> /"SSLmode"="allow"/
> /"XaOpt"="1"/
> /"KeepaliveTime"="-1"/
> /"KeepaliveInterval"="-1"/
>
>
> Maybe this can help you in debugging?
>
>
>
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> schrieb am Di., 12. Jan. 2016 um
> 00:21 Uhr:
>
> On 01/11/2016 06:26 AM, Walter Willmertinger wrote:
> > I installed the new version. Normal connection test was OK, but
> not the
> > special connection test in "Page 3".
> >
> > Using a postgresql database (8.4.22) with MS Access 2013 seemed
> to work,
> > but only read access. As soon as I try to change some data, I get the
> > message "Another user has changed ...".
> > I uninstalled the new version and installed the last release, now
> it is
> > working again.
>
> When you ran the new version did you see if Row Versioning was checked?
>
> >
> > Regards, Walter
> > --
> >
> > Viele Grüße
> >
> > Walter Willmertinger
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>
> --
>
> Viele Grüße
>
> Walter Willmertinger
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com