[AccessD] Find First in an Array?

Jennifer Gross jengross at gte.net
Fri Feb 20 16:09:20 CST 2009


If only I disagreed with you on bound forms and PKs, this would be the
time to strike ;)

Jennifer

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Friday, February 20, 2009 1:42 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Find First in an Array?


ROTFL.

Who is this "great John Colby" guy?  Sounds like a magician or escape
artist or something.

When I think about "static data tables in the FE" (which isn't often!) I
always thought of it in the 
"list table" context.  Colors, gender, state, etc.  My applications have
so many list tables that it 
makes no sense TO ME to get into a "this one should, this one shouldn't"
kind of thing.  I just 
leave all such tables in the BE.  I have enough things to think about
without spending time on stuff 
like that.  If the table doesn't change much but impacts performance I
cache it.  Otherwise I don't. 
   I mean think about it, "list tables in the FE" are a cache of sorts,
you are "caching" them in 
your FE on your local hard disk.

My problem with the concept is simply spending time on evaluating the
"content change" issue for 
each table.  Obviously you can't cache (for example) a city table in the
FE if the user can add 
cities on a daily basis.  The state table OTOH probably never has
records added.  So you spend time 
trying to think about which should and which shouldn't.  Get it wrong
and the database starts to 
break.  Basically any table in the FE simply cannot be updated by users.

Bahhh.  Data belongs in the BE, not on my desk making case by case
decisions.

Having said that, our good friend Jürgen Welz has an application where
caching everything he could 
in the FE made perfect sense.  His FEs had to work over very slow lines,
over the internet IIRC and 
every byte of data transferred over the wire mattered.  My clients OTOH
don't do that so I just made 
a decision to spend my time on other things.

I truly have never run into tables that were so FE specific and had
ancillary reasons (sending out 
for translation) to have them in the FE.

Anyway... glad I could light up your day.  8~)

John W. Colby
www.ColbyConsulting.com


Jennifer Gross wrote:
> Wow, to sway the great John Colby.  And in a "religious" argument no 
> less.  Now that made my day.
> 
> Seriously smiling,
> 
> Jennifer
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Friday, February 20, 2009 1:05 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Find First in an Array?
> 
> 
> Now there is a reason that places the whole issue in a new light. 
> Language data is indeed specific to a particular FE in a way that most

> other data is not.  So perhaps for that specific task, a table
> in the FE makes perfect since.  I would STILL cache it but that is
> another issue.
> 
> Thanks Jennifer,
> 
> John W. Colby
> www.ColbyConsulting.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.1/1961 - Release Date:
02/19/09 18:45:00






More information about the AccessD mailing list