[AccessD] Find First in an Array?

Or putting the static information into xml files and including them with
your application.  That's basically what we do with similar information
in .Net, stuff like units of measure and lookup codes.

Chrlotte Foust 

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

Pot - Kettle - Black?

Instead of relying on "accepted practice", maybe you should think about
it.

You are missing the whole point of putting the translation tables, menu
tables etc in the FE.
It's nothing to do with speed.

This type of "program" data falls into a completely different category
to the "operational" 
data in the BE.
It is guaranteed to be static for the life of the FE and is almost
certain to change with each new FE version. 

One of the primary advantages of splitting an Access application into
FE/BE is the ease of updating the application without touching the
"operational" data simply by dropping a new FE in the appropriate
location(s).  As soon as you put this "program data" into tbe BE, you
have to jump through hoops to update your application.


--
Stuart

On 20 Feb 2009 at 16:01, jwcolby wrote:

> Often a belief is created in the distant past when we make a decision 
> of some sort that sways the argument in one direction or the other.  
> We often then stop "thinking" about it and simply "believe" it.  If 
> enough time passes, we may completely lose track of why we even
believe something.
> 
> In this case I would guess that those who place such tables in the FE 
> have either never thought of or considered caching it, or considered 
> and rejected it.  In those cases having it in the FE solves a speed 
> problem.  Now these people have "solved" their speed problem and the
"reason" fades into a belief.
> 
> I started using data caches some time ago and, while I never used data

> tables in the FE even before that, having the cache simply makes the 
> FE Data Tables concept a non-starter.  In all other respects
> (IMHO) having data in a BE is the accepted practice.  Since my caches 
> solve my speed issues I truly do not need them in the FE.

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