From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Garner Chung <garner(at)nuws(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Extra Opts = Ox2 (Fake MS SQL Server so that MS Access |
Date: | 2006-10-11 06:14:19 |
Message-ID: | 452C8BBB.9060409@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-10-11 07:23:58 | Re: New release of psqODBC? |
Previous Message | Hiroshi Inoue | 2006-10-11 02:27:04 | Re: New release of psqODBC? |