Re: psqlODBC 09.00.0310 and oids

Hi Nirgal-san.

Sorry very late reaction.

Umm, I can't explore your problem....
Office 97 is very old which does not reach it for me.
although I use 2003, I don't look at a problem.
For example,
http://winpg.jp/~saito/psqlODBC/check/FakeIndex.png

Regards,
Hiroshi Saito

(2011/07/12 18:26), Nirgal Vourgère wrote:
> On Friday 08 July 2011 21:08:21 Hiroshi Saito wrote:
>> Changes and updates in the new release include:
>> 5.) Handle *with or without oids* correctly.
>
> Thank you very much.
> However, the behaviour is still no exactly what I expected:
>
> I have a legacy excel 97 database, poorly designed, with about 100 tables, 1000 queries, complex forms... You get the picture.
> I used a recent mdbtools snapshot from git to convert the database to postgres (index, default values, constaints, this rocks!).
> However, I had a lot of tables without a primary keys.
> What I did is adding oids for these tables, and created a primary key (on oid).
>
> Now, I still have some legacy code from access I'd like to use.
> I changed the access tables to psql linked tables, and I'm opening the connection with that:
> ODBC;CA=r;A6=;A7=100;A8=4096;B0=255;B1=8190;B9=0;BI=0;C2=dd_;CX=1b102bb;A1=8.4;DSN=india;SERVER=10.10.10.146;DATABASE=india;PORT=5432;UID=jvourger;PASSWORD=xxxxxxxx
> (This is CX with BIT_SHOWOIDCOLUMN)
> But when open these tables with a primary key on oid, I don't see the oid column and I can't append data.
>
> I also tried CX=1d102bb (BIT_FAKEOIDINDEX). Same results.
>
> Does anyone has any idea about what is going on?
> Is that an excel problem? Or is there some change I could make in psqlodc to have these linked tables work with legacy access modules?
>