Lars asks,

> >As for the duplicates - lower powered CPUs and/or PCs with low memory do
> >have this problem with Access and Linked Tables.  You may try
> this on a PC
> >which is at least (...)
>
> As English is not my native language I might have misunderstood that part
> of the posting... To me this sounds as if a faster/bigger/better PC may
> not only return/display results faster then a
> slower/smaller/boughtlastweek
> PC, but it also might have a higher chance of yielding _correct_ output??

Actually, I was talking about Window refresh, as well as handling things
like returned rows.  JET will, if read only, normally return a "Snapshot"
type Recordset, in which all of the data requested is returned (and cached).
A Read/Write - enabled query will normally return a "Dynaset" type
recordset, where a keyset only is retrieved, as well as the first "x" rows -
all of which is cached.

Again - when I said "there's a lot going on in there" - it's just not
Access, but also ODBC Manager, the driver itself, and depending on the
amount of data being accessed - one heck of a lot of network traffic and
data handling by the DBMS Engine (JET) itself.

Hope this clarifies things a bit...

Best,
Joe