Re: Ctrl+F in MsAccess table is very slow

From: Arnaud Lesauvage <arnaud(dot)lesauvage(at)laposte(dot)net>
To: David Gardner <david(dot)gardner(at)yucaipaco(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Ctrl+F in MsAccess table is very slow
Date: 2007-03-23 12:51:05
Message-ID: 4603CD39.3010108@laposte.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

David Gardner a écrit :
> Try this with and without the Declare/Fetch option checked. Also this
> may be a situation where you may have an index on your varchar field,
> yet Access doesn't know about it.
>
> Also what datatype does Access think the field is? I have run into
> problems where Access will think the text datatype is a Memo field (FAQ
> 6.5 & 6.6). While on the subject of Access being weird is either your
> index field or the codelocalite field declared as int8(bigint)?

Hi David,

Turning on or of UseDeclareFetch apparently makes no difference.
But you are right that the field is indexed and that Access doesn't know about it (probably because the linked table is a view, not a real table ?).

Apart from that, the field is a varchar and Access sees it as such, and codelocalite is an int4 field, so I think everything is fine here.

Regards,
--
Arnaud

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message noreply 2007-03-23 15:50:21 [ psqlodbc-Bugs-1001827 ] Error when updating a TIMESTAMP column with NULL using ADODB
Previous Message Hiroshi Inoue 2007-03-23 04:20:26 Re: Erro on the latest version