[AccessD] Managing Lookup Tables

Hello All,

After reading everyone's response...I see the benefit to each 
suggestion...but the reason listed below puzzles me.  When you say 'nuke' 
the data...do you mean deleting all rows?..and if so...why not just delete 
from the tables you want.

I do something similar...on a smaller scale(30 to 40 concurrent users).  FE 
on the user machine...BE on the network...when the FE opens...it checks for 
a new FE...copies down if so...if not checks links...relinks as 
necessary...and if it is the first time they are launching today...it copies 
all lookup tables from the BE to the FE...and all lookups are done locally.  
Initial startup takes about 20 seconds...but this is acceptable for my 
users.  I did this for speed of the lookups...and didn't see the need to put 
in a 3rd db.

Not sure if it is even relevent since I don't understand the reason.

Thanks,

Mark A. Matte


>From: "Arthur Fuller" <artful at rogers.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "'Access Developers discussion and problem 
>solving'"<accessd at databaseadvisors.com>
>Subject: [AccessD] Managing Lookup Tables
>Date: Tue, 11 May 2004 11:10:04 -0400
>
>I have been trying to devise a cool way of managing lookup tables v.
>"data" tables. I.e. PaymentTypes v. Payments. It occurred to me that I
>could maybe link to two different back ends, one containing only the
>lookup tables and the other containing only the data tables. What I
>don't like about this approach is that I tend to define everything I can
>at the table level -- Caption, lookup, validation criteria, etc. etc.. I
>know this is controversial, and I don't want to rekindle those threads.
>What I am wondering instead is, Suppose I link the front end to the data
>database, and then link it in turn to the lookups database. I'm going to
>build 3 toy databases to check this out, but I'm wondering if anyone can
>see any significant problems in this approach.
>
>My basic reason for wanting to do this is so that I can freely nuke all
>the data in the data database, while preserving all the data in the
>lookup database.
>
>Insights, advice, and cash donations appreciated :)
>Arthur
>
>--
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

_________________________________________________________________
Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com