Re: Extra Opts = Ox2 (Fake MS SQL Server so that MS

From: "Garner Chung" <garner(at)nuws(dot)com>
To: "Hiroshi Inoue" <inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Extra Opts = Ox2 (Fake MS SQL Server so that MS
Date: 2006-10-11 17:38:04
Message-ID: 6FB011BE26AACD4CB5F2B505AE0BEB2E0204C07F@MI8NYCMAIL05.Mi8.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hiroshi-san,

We tested it, examined the logs and can report that the problem is fixed
in the snapshot we downloaded this morning. Because so much of our work
hinges on the psqlODBC driver right now, we especially appreciate the
quick turnaround. Thank so much for the help.

Yay for open source! Boo bugs.

garner

-----Original Message-----
From: Hiroshi Inoue [mailto:inoue(at)tpf(dot)co(dot)jp]
Sent: Tuesday, October 10, 2006 11:14 PM
To: Garner Chung
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Extra Opts = Ox2 (Fake MS SQL Server so that MS
Access recognizes PostgresSQL's serial type as AutoNumber type)

Garner Chung wrote:
> Hey Gang,
>
> We've been working hard here trying to get our rather large MS Access
> application to work with PG as its backend. At a gross level, that
> means keeping our existing forms and reports while instead pointing
> them to our new PG backend using the psqlODBC driver. We have learned
> a tremendous amount in the process -- gaining a better understanding
> of architecture and idiosyncracy alike.
>
> Right now, we're snagged on what seems to be a bug lying somewhere in
> the ether where DAO, ODBC and psqlODBC meet. It centers around the
> ability to insert into a table with a numeric ID field of type serial.
> There is an Extra Opts parameter, 0x2, that one can set in the DSN to
> get Access to map fields of type serial to its own native type of
> "Autonumber". With this in place, one is able to append a new row to
> an open record set that is bound to that table. This can be done in
> Access with either the DAO Recordset AddNew method or by appending the

> record in the Datasheet view of the linked table in Access. The main
> trick here is ODBC's ability to ascertain the last sequence value
> generated by the insert. However, we're finding this functionality is
> failing when the table contains a field of PG type text(mapped to
Access type memo).

Please try the snapshot dll at
http://www.geocities.jp/inocchichichi/psqlodbc/index.html
.

regards,
Hiroshi Inoue

Browse pgsql-odbc by date

  From Date Subject
Next Message Tony Caduto 2006-10-11 17:57:06 Re: Access2000 & sequence as primary key in view : #DELETED
Previous Message Arnaud Lesauvage 2006-10-11 16:49:34 Re: Access2000 & sequence as primary key in view : #DELETED