artful at rogers.com
artful at rogers.com
Tue Feb 20 10:35:47 CST 2007
Personally, I wouldn't keep the aliases in a separate table, for exactly one reason. Suppose that during my criminal career I had the following aliases: Arthur Harkins Arthur Hindman Alphonse Carbonnell Arthur W Colby Arthur G Brock Arturo Francisco Tapia etc. Presumably all these are tied to the birthname of the malfeasant Arthur Fuller. I would keep them all in a single table, with a column in it called OriginalPK, that was based on some unique identifier such as SSN or SIN (in Canada). For police applications, I think this is permitted. At any rate, I don't care that Arthur Hindman uses the alias Arthur Colby; what I care about is that Arthur Fuller has many aliases. This could be achieved with separate tables, but I don't really see the advantage to doing so. There is also the (potential) issue that the miscreant in question stopped using a particular alias at some point. Arthur Fuller Technical Writer, Data Modeler, SQL Sensei Artful Databases Organization www.artfulsoftware.com ----- Original Message ---- From: Susan Harkins <ssharkins at setel.com> To: Access Developers discussion and problem solving <accessd at databaseadvisors.com> Sent: Tuesday, February 20, 2007 11:01:53 AM Subject: Re: [AccessD] combo from multiple sources At one point I wanted to show every name associated with a case in a combo to identify which name was used. This included alias's which were in a different table. So I needed data displayed from 2 different tables...and I just used a UNION query as the source. Does this address your question? ==========About the rant? Nicely done. :) As for the combo box -- it would be for display? You weren't using it to filter other data? Sounds like an interesting project btw. :) Susan H. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com