My primary key selection is solid and duplicates will never occur. I played with this for awhile and used a table data macro with the Before Change event to make this work the way I need it to.
Thanks!
I should have told you that I have the code to do this in a query already and I'm looking for a way to have this automated and thought a table event after insert might be the way to go.
I see that Access 2010 does support table events. I would like to use the After Insert event to concatenate the data in two columns and place the resultant in a third column. Can someone tell me where I can find a good reading resource to develop this logic.
I do respect your commentary and in my previous post I mentioned that I was able to recognize the duplication and I have reduced this to four tables, which include the following:
tbl_instrument_list
tbl_datasheets
tbl_junction_notes
tbl_notes
I now see the error in my ways and I thank for...
Forget the previous comment. That whole mess is now down to four tables and I can already appreciate the ease of building my sql queries. I use Sybase Powerbuilder on the front end. Thanks again!
I understand your comments. Datasheets do have unique columns based on the datasheet type and so if I combine them into one table, then it would seem that I would violate 2nd normal form since all columns are not related to the primary key. However, I could reduce the number of datasheet...
I know that Access has a table limit of 32 indexes. I have a table with one primary key and that primary key column is indexed with no duplicates allowed. I have 36 other tables that would like to have a foreign key relationship to this table's primary key. Only 32 are accepted due to the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.