Great technical term. I'm gonna steal it. Sounds like you need an AfterUpdate event. Make a change, and then use AfterUpdate to plop that data wherever else you need it. However, if you're dealing with other tables, you may need an SQL statement to insert/append a record, or an update. Without knowing more about how your database is set up, it's hard to tell you what lesson to watch.

'm going to attempt to explain what I'm doing or "trying to do."
My database has 208 fields.  24 of those fields pertain to general information about the Corp.  (Date of Incorp, Month of Annual Return, are we the registered office, who's the accountant and banking and contact person for the Corp.  etc.) Then I have the fields for the Directors and the Shareholders of the Corp.  For the Directors, I need to know name and contact info, if they are a shareholder and if it's voting shares what their office is (President, Secretary-Treasurer etc.) (I have eight sets of these)
For the Shareholders, the same contact info as the Directors, but I also have to know the type and amount of shares they have in the company, as well as the kind of share -  voting, non-voting, common or preferred etc. (I have eight sets of these well).  So I use the database to create Incorporation Docs, Share Certificates, Debentures, Resolutions, Unanimous Shareholder Agreements, Share and asset sales, Dividends etc

....Some documents are signed only by Directors, others only by Shareholders.  There are so many different combinations of the directors and shareholders in a Corp.; in most cases, if a person is a director, they will usually hold shares in the company, But not all Shareholders are Directors. So I was thinking about how I could reduce the number of times I have to type the same info into different fields; maybe I could make a single field with a check box that would say yes, this person is a director, and then I could merge with my documents for just directors and my documents for just shareholders.   Does any of that make sense?

Yes. It's makes perfect sense. Do you have all of these fields in one table? If so, then you could copy and paste the names to different fields, but that's wasteful. Sounds to me like putting people into categories would be your best bet. I would have one table for the corporation (CorpT) and then another table for the people in that corporation (PersonT). If ALL you're dealing with is directors and shareholders then you could just make two fields in your table: IsDirector, IsShareholder. Then you could use those fields to put the people in the appropriate reports. If you want more categories, make a third table to put them into groups (and a fourth junction table with a many to many relationship like I show in Access Expert 7)

Hello, sorry for delay in response.  Yes I do have all fields in one massive table.  I can easily split them into separate tables as you've suggest. My biggest thing is how to get the info I want to  "plunk" into  the fields I want and Not when I don't.  If I'm understanding relationships correctly its hard-fast connection.  Might have to tweak the forms  a button for "these ppl are both directors and shareholders" and a button for these ppl are not kind of a thing.

If you want to keep it all in one table, you could add fields for IsShareholder (y/n), IsDirector, etc. Then when you check those boxes ON, copy the names to the appropriate other fields you need them in with an AfterUpdate event. There's a million ways you could do it. Even create a button that says "copy all names now" and do it that way.

Well I am now "Normalizing" my database....  typical me zooming ahead, no driving 55....

That's good. Progress! :)