Hi
I have an Access 2003 database for tracking requested updates to Standard Operating Procedures in work. Currently I have just 1 table with fields for SOP Number, Details of update & other specific details like requestor & date. Any 1 SOP number can have a number of updates logged against it, & I understand that strictly speaking, information should only exist once in databases. That would mean having another table for SOP numbers & establishing a relationship between the 2 tables.
It would not be practical to populate the SOP number table with all SOPs, in case new SOPs get written, but would it be possible to write code to have Access check if the SOP number is in the table, & if not then add it in?
Thanks
I have an Access 2003 database for tracking requested updates to Standard Operating Procedures in work. Currently I have just 1 table with fields for SOP Number, Details of update & other specific details like requestor & date. Any 1 SOP number can have a number of updates logged against it, & I understand that strictly speaking, information should only exist once in databases. That would mean having another table for SOP numbers & establishing a relationship between the 2 tables.
It would not be practical to populate the SOP number table with all SOPs, in case new SOPs get written, but would it be possible to write code to have Access check if the SOP number is in the table, & if not then add it in?
Thanks