Skip site navigation (1) Skip section navigation (2)

Re: ODBC driver adding extra characters to table names.

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "Paul Lambert" <paul(dot)lambert(at)autoledgers(dot)com(dot)au>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: ODBC driver adding extra characters to table names.
Date: 2007-08-16 09:29:30
Message-ID: 005801c7dfe7$f291cf70$c601a8c0@HP22720319231 (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi.

From: "Paul Lambert" <paul(dot)lambert(at)autoledgers(dot)com(dot)au>

> Steps to reproduce:
> 0) Make sure standard_conforming_strings is turned ON and pg has been 
> restarted.
> 1) Open up MS Access (2000 and 2003 both give me the problem)
> 2) Go to tables section, right click and select link table.
> 3) Find your ODBC data source.
> 4) Select public.billing_code from the list of tables.
> 5) Error is presented at that stage (don't even get to the point of 
> writting a select query)
> 
> I can attach the full mylog if you so wish - I haven't put it on yet 
> because the log created from just that one query is around 800K so I'm 
> leaving it off unless it's specifically requested.

I pointed out the problem of TEXT-field involving this. Furthermore, your 
problem was in others again... Do you use FAKEOIDINDEX? 
Probably, Turning it OFF may help.

However, It is necessary to continue TEXT-Field problem.

Regards,
Hiroshi Saito


In response to

pgsql-odbc by date

Next:From: Lothar BehrensDate: 2007-08-16 11:35:15
Subject: Re: UPDATE with data at exec and CURRENT OF question
Previous:From: Hiroshi SaitoDate: 2007-08-16 08:16:34
Subject: Re: UPDATE with data at exec and CURRENT OF question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group