[AccessD] ...for AD and anyone with an idea

William,

  I haven't seen the code, but using .Seek on an index is the fastest way to
find something with JET.

  With 38K+ records, your definitely in that territory if you want fairly
quick (sub second) response.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman
Sent: Wednesday, February 17, 2010 2:42 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] ...for AD and anyone with an idea

AD

...I'm trying to implement your Match Similar Address sample (from Roger's 
site) in a client app.
...I'm working against a linked table w/38k+ records and it is impossibly 
slow
...I imported the relevant fields into a local temp table and replaced the 
DCount with a standard replacement function
...its faster ...but only marginally ...still impossible to deploy to client

users

...any ideas on how I can speed this up?

...I considered splitting the records using some criteria but that 
essentially eviscerates the primary purpose of the code in the first place.

...any ideas appreciated ...it's a sweet little piece of code and works well

on small tables ...but that's not what I have.

William 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com