[AccessD] Managing Lookup Tables

I have several that do this.  All the lookup tables are in dbReference.
The data tables are in their own databases. I link the reference table
and the data tables to the appropriate front ends.  
Has been working quite well for about 4 years now. It allows me to
maintain the reference tables ONCE for all the systems, no need to hunt
through 4 systems and determine whether they use that particular lookup.

The only validation I do at the table level is default value and maybe
caption but for the most part that occurs in whatever routine is
receiving or sending the data.

Patti

******************************************************************
*Patricia O'Connor
*Associate Computer Programmer Analyst
*OTDA - BDMA
*(W) mailto:Patricia.O'Connor at dfa.state.ny.us
*(w) mailto:aa1160 at dfa.state.ny.us
******************************************************************
 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Arthur Fuller
> Sent: Tuesday, May 11, 2004 11:10 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Managing Lookup Tables
> 
> 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
> 
>