 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 2 / May 2007Avoid Duplications
I have 2 tables which are absolutely identical On top of these tables I have forms, queries and reports I am looking for a method that I can use one version of the above for both tables Specifically is it possible to set the source of a report at runtime, how can I set a variable within a form before opening it so that will be the basis of all the rest Thank you, Samuel Why do you have two "absolutely identical tables"? There is no valid reason for this in a normalized relational database. Delete one table and you should be all set.  SignatureHope that helps! RBear3 . >I have 2 tables which are absolutely identical > [quoted text clipped - 9 lines] > Thank you, > Samuel The tables are identical in structure but they are used for 2 different types of data > Why do you have two "absolutely identical tables"? There is no valid > reason for this in a normalized relational database. [quoted text clipped - 14 lines] >> Thank you, >> Samuel > The tables are identical in structure but they are used for 2 > different types of data I suggest that you may want to combine both tables and add one additional field to identify the different types. It is hard to say for sure since I don't know enough about your data, but it sounds like that would be the preferred way and would solve your problem. >> Why do you have two "absolutely identical tables"? There is no valid >> reason for this in a normalized relational database. [quoted text clipped - 20 lines] >>> Thank you, >>> Samuel SignatureJoseph Meehan Dia 's Muire duit I would agree with Joseph. Normalization rules would suggest that this data should be in one combined table with a separate field to help filter. A good example of this is "Employees" all in one table with an "inactive" checkbox to allow you to pull only active or inactive. SignatureHope that helps! RBear3 . > The tables are identical in structure but they are used for 2 different > types of data [quoted text clipped - 17 lines] >>> Thank you, >>> Samuel Please trust me that there is a good case for having 2 tables due to the fact that there are a lot of functionality already built on top of the existing table and practically speaking it is the only way to avoid mistakes in this important part of the system. However, I do want to share some of the existing functionality (forms reports etc.) and I wonder if anyone can help me as I described in my initial email Thank you, Samuel >I would agree with Joseph. Normalization rules would suggest that this >data should be in one combined table with a separate field to help filter. [quoted text clipped - 22 lines] >>>> Thank you, >>>> Samuel > Please trust me that there is a good case for having 2 tables due to > the fact that there are a lot of functionality already built on top [quoted text clipped - 7 lines] > Thank you, > Samuel If that is the case, (I can't think of an situation where it would be however) then I suggest you just make copies of what you have to have two sets of the forms reports and queries each applied to one table. It is not likely to bloat the size of the database that much. SignatureJoseph Meehan Dia 's Muire duit |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.