Synchronizing two data sets

I am transitioning from VB6 to Enough of that...

For verification sake I want to confirm best practices.

1. I have two forms sharing a common dataset from an Access 2013 database. Form1 uses the table "contacts" and form2 uses the table "notes". They both share a common field "contactID"
2. My thinking is that when I open Form2 (notes) to update any notes to be stored from the open contact from Form1, I can just insert a parameter into the query searching the common 'contactID'. If there are no records found I can create stub record using the contact ID. If the user changes their mind, an update will not be called.

We all know there are hugely conflicting opinions on every issue possible on the internet. I've read some articles that believe this is the dumbest thing they've ever heard of and others that think it's just fine. I hate doing things twice.

1. Is this best (or acceptable) practice?
2. If not best or acceptable can I get some guidance on what would be?

Many thanks
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Russell FoxDatabase DeveloperCommented:
If I'm understanding you correctly, the user will have Form1 open, looking at a specific contact, and then perhaps push a button to open the notes form, Form2, for that record? Assuming the forms have a standard recordset, that is they're attached to a table, query, or linked table, you can just add the ContactID from From1 as the "filter" for Form2, something like "ContactID=Forms!Form1.ContactID.Value". If you're doing everything via code, filling the forms with recordsets created by dynamic SQL via VBA, then you'll need to pass the Form1 ContactID as part of the WHERE clause. Unless I'm not understanding the question.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SchoolTeacher54Author Commented:

You understood the question. My brain really got bent by some of the articles that I read as if there is some magic going on with .net.

I'll carry on feeling better about the whole thing now. Thank you.

Russell FoxDatabase DeveloperCommented:
Yeah, in Access there's at least five ways to get anything done, and it's often hard to tell which one is best!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.