Access/Postgresql problem with text fields recognized as memo

From: Justin Dahl <justind_lst(at)ussonet(dot)net>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Access/Postgresql problem with text fields recognized as memo
Date: 2005-02-08 21:50:35
Message-ID: 4209342B.7090607@ussonet.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

I've ran into this problem before and then abandoned it out of
frustration, I'm coming back to it again.

Using Access 2000
Postgresql 7.3.4
ODBC driver 7.03.02.00 on WinXP

All tables I create have a unique index called "id" that is of type
"serial".
Setting "Row Versioning" in odbc driver does not make any difference.

If a table is created with 3 columns

id (serial)
field1 (varchar(255))
field2 (text)

This table is linked into an access file.

If data is typed in at the table view of the file.

Scenario 1:
Only a value is filled in for field1.

The information is inserted normally and everything is happy and good.

Scenario 2:
Information is filled in for both field1 and field2.

The information is inserted normally and everyting is happy and good.

Scenario 3:
Only a value is filled in for field2.

The information is inserted normally, but all fields will display
#Deleted across them appearing to the user to have failed.

Scenario 3 is what is bothering me the most. I have done quite a bit of
testing with this and this only occurs in conjunction with fields
recognized as type "memo" by access.
Please keep in mine that I have a unique index field called "id". The
same thing occurs wheather "Row Versioning" is turned on or off on the
driver.

I lean towards this being a MSAcess issue, can anyone give any input on
this and how i could correct it? Let me know if more info is needed.

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2005-02-09 07:10:10 Re: Unix domain socket
Previous Message Justin Cranford 2005-02-08 16:47:08 v07.03.0200: Make errors if configured --with-odbcver=0x0100