Shamil Salakhetdinov
shamil at users.mns.ru
Sat May 12 12:23:21 CDT 2007
Yes, Rocky, This "gray area" tblFAB table is more a lookup than production table in my opinion. Of course in other application e.g. the one, which could be used to prepare data (insert. Update, delete) for your tblFAB table on regular basis in a company/institution, which designs technological processes for metal cutting and stamping operations, this tblFAB table will be considered a production not lookup table... -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Saturday, May 12, 2007 6:54 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Lookup and productiontables'alternativesymbolickeys... Shamil: I have an app which chains five tables together - in a query as the basis of a report. (The application is a production system for a metal cutting and stamping operation). Is this the kind of thing you're referring to? A couple of these tables are clearly production tables by your definition, but others fall into a gray area. For example, one of them - tblFABs - is fairly static but contains 41 fields including the autonumber primary key, and contains information about how a job is processed and specification. Where the user needs to select a FAB number I use a combo box with just the autonumber (width zero) and the FAB number. But I think this is pretty standard programming technique. Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: Saturday, May 12, 2007 7:33 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Lookup and productiontables'alternativesymbolickeys... John, My experience shows that within a database (developed for small/middle size businesses) there are usually a few *core* production tables, which are getting updated (rows inserted, updated, deleted (marked as deleted)) often. All the other tables are getting updated not that often and they are mainly used as *lookup* tables for the few *core* production tables. IOW here lookup is meant in a broad sense. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Saturday, May 12, 2007 4:58 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Lookup and production tables'alternativesymbolickeys... Shamil, I consider a lookup table to be small simple tables such as state, color, product type etc. Definitions like this are definitely gray areas, and if you apply the criteria "how often are they change" then I see where the chains would be much shorter. In the call center database, the "changes" would start at the claimant / claim / benefit / BeneCheckInfo / Check. There are cases where the same claimant has multiple claims, but MOST of the time you start with a new claimant. That often reaches back up to the policy holder / policy portion of the chain if that policy holder has never been entered before, which is less common than a new claimant. Given that I have a framework 8-) I can (and am able to) track all form usage, so I could do some statistics as to which forms are used how often. I just went and checked and I have the object tracking turned off so I would have to turn it on and wait a few weeks to get meaningful results. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: Saturday, May 12, 2007 6:38 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Lookup and production tables' alternativesymbolickeys... Hello Stuart, Thank you for your sample: this looks for me more as "lookup up chain" - a kind of 6 levels classification system for a Voter. I obviously missed to mention such cases in my first posting. IOW: Province->District-> Local Level Government Area->Ward->Locality->Location is in my opinion a lookup tables' chain Area->Ward->Locality->not a master->detail->...->detail chain of production tables. Of course all depends on point of view: I'd distinguish lookup and production tables based on probability of how often their data is getting changed... BTW, do you have autonumber/identity keys for all your tables? do you also have (alternative) symbolic keys for your tables? Thank you. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Saturday, May 12, 2007 2:14 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Lookup and production tables' alternative symbolickeys... On 12 May 2007 at 13:52, Shamil Salakhetdinov wrote: > BTW, what was the longest master->detail->...->detail chain for a > database you developed? > > >From my experience an average value for the length of these chains is 2.5; > if it's 3 then the third level table is usually a (many to many) > relationship table; sometimes length of chains can be even 5 but I > have never seen chains longer than five... > > Do they exist? I'm currently working on an Electoral roll which has a seven level chain: Province District Local Level Government Area Ward Locality Location Voter -- Stuart -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.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 Free Edition. Version: 7.5.467 / Virus Database: 269.6.8/800 - Release Date: 5/11/2007 7:34 PM -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com