Re: Ctrl+F in MsAccess table is very slow

From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
To: David Gardner <david(dot)gardner(at)yucaipaco(dot)com>, Arnaud Lesauvage <arnaud(dot)lesauvage(at)laposte(dot)net>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Ctrl+F in MsAccess table is very slow
Date: 2007-03-21 16:12:21
Message-ID: 339069.33165.qm@web31811.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc


--- David Gardner <david(dot)gardner(at)yucaipaco(dot)com> wrote:
> 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)?

I've seen this Memo applied to non-dimentioned varchar() fields, Even ones that were indexed. I
haven't had any problems with slow filtering rows, but to be fair my database only has 1/30 the
number of records.

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message noreply 2007-03-22 00:18:43 [ psqlodbc-Bugs-1001827 ] Error when updating a TIMESTAMP column with NULL using ADODB
Previous Message David Gardner 2007-03-21 15:55:38 Re: Ctrl+F in MsAccess table is very slow