[AccessD] Managing Lookup Tables

Arthur,

You can do it the way you envision and shouldn't have a bunch of
problems ... Unless you get tangled in replication.  I've often built
applications on this 3-database plan, but you need more robust code for
handling relinking and testing the links,  since testing only one
database or relinking only one isn't enough.  We do something similar
with our commercial apps in this company, so I know it works on a broad
scale.  I must admit that I haven't tried it with MDEs, though, so maybe
someone else can contribute on that point.  

Charlotte Foust 

-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com] 
Sent: Tuesday, May 11, 2004 7: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