[AccessD] A Question of Timing

From: "Jim Dettman" <jimdettman at verizon.net>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Thursday, January 04, 2007 11:36 AM
Subject: Re: [AccessD] A Question of Timing


> I'd follow gustav's advice and use seek.  I also wanted to add that you 
> can
> use seek on a remote teable, but you must open the remote database first.
> See code below.
>
> Jim.
-----------------------------------------------------------------------------
> Also, If you ship this thing with a table with all languages, you could 
> look
> up a "language" flag as the FE opens, run a query that pulls only records
> for that language out into the recordset, then store all those phrases in
> the collection.  In essence, the correct language loads into a collection 
> as
> the form opens, and then is available as required from that point on.  I
> call this caching since that is really what it is.  Collections are orders
> of magnitude faster than tables for this kind of thing, and their
> performance won't decline as the number of users in the db grows.

> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com


Hmm. Now I'm curious. The 'orders of magnitude' wasn't spoken
against and yet Jim still went with seek. Any particular reason, Jim?

Michael R. Mattys
MapPoint & Access Dev
www.mattysconsulting.com