 which can link to one or more tables?

I was wondering if someone can help me with a normalisation issue I am facing, when trying to create a seperate communication table, for a personal project I am working on. Lets say I have the following tables and table columns:

Table A:
Table_A_Id, Date, Name, Agent_Id (FK), Notes
Agent Table:
Agent_Id, Date, Name, Phone, Email, Notes
Direct Contact Table: 
D_C_Id, Date, Name, Phone, Email, Notes

Above is a sample of my actual tables, but describes my issue.
Essentially to normalise the above table to 1NF, I need to split the Notes column into its on seperate table, to help make the tables atomic, and comply with the 1NF rules. I want to split it out to a seperate column called Communication Table, which can allow me to keep track of when I made a conversation relating to the respective table and what I discussed.
I am not sure how to best to handle the split out Communication Table. because the Notes in Table A also links to an Agent from within the table, however the Notes column in the Agent table, only relates to communications done with the Agent.
So which of the following would you recommend is best for communication table:
EXAMPLE 1:
COMMUNICATION TABLE
Com_Id, Date, Link_Table, Link_Table_Id, Notes

Here the Link_Table should define what specific table is being dealt with and Link_Table_Id is the specific Id on the Link_Table

UPDATE:
Sorry I forgot, I need to also add another column called Communicated_With to the above, because there may be instances where communication related to Table A, could occur with another agent or person.
So the table would look like:
Com_Id, Date, Link_Table, Link_Table_Id, Communicated_With, Notes
OR
EXAMPLE 2:
COMMUNICATION TABLE
Com_Id, Date, Table_A_Id, Agent_Id, D_C_Id, Notes

Here all the unrelated Id columns would have to be set to null, whilst the related colum defined with an Id.

OR
EXAMPLE 3:
COMMUNICATION TABLE
Com_Id, Date, Notes

Here all other tables have a foreign key to
which can link to one or more tables? 

 I was wondering if someone can help me with a standardization consequence I am facing, when trying to make a seperate communication board, for a personal project I am working on. let read I have the following table and table columns: 

 board A: 
 Table_A_Id, Date, Name, Agent_Id (FK), Notes 
 Agent Table: 
 Agent_Id, Date, Name, Phone, Email, Notes 
 Direct Contact Table: 
 D_C_Id, Date, Name, Phone, Email, Notes 

 Above is a sample distribution of my actual tables, but describes my issue. 
 Essentially to normalise the above table to 1NF, I need to divide the Notes column into its on seperate table, to help make the mesa atomic, and comply with the 1NF rules. I want to split it out to a seperate column call Communication Table, which can allow me to keep track of when I made a conversation relating to the respective mesa and what I discussed. 
 I am not sure how to best to handle the split out Communication Table. because the Notes in Table A also links to an Agent from within the table, however the Notes column in the Agent table, only relates to communications done with the Agent. 
 So which of the following would you recommend is best for communication mesa: 
 EXAMPLE 1: 
 COMMUNICATION TABLE 
 Com_Id, Date, Link_Table, Link_Table_Id, Notes 

 Here the Link_Table should define what specific table is being deal with and Link_Table_Id is the specific I d on the Link_Table 

 UPDATE: 
 Sorry I forget, I need to also add another column call Communicated_With to the above, because there may be instances where communication related to Table A, could occur with another agent or person. 
 therefore the table would look like: 
 Com_Id, Date, Link_Table, Link_Table_Id, Communicated_With, Notes 
 OR 
 EXAMPLE 2: 
 COMMUNICATION TABLE 
 Com_Id, Date, Table_A_Id, Agent_Id, D_C_Id, Notes 

 Here all the unrelated I d columns would have to be fructify to null, whilst the related colum defined with an Id. 

 OR 
 EXAMPLE 3: 
 COMMUNICATION TABLE 
 Com_Id, Date, Notes 

 Here all other table get a alien key to
 whlch can link to one or mure tables?

I was wondermng if aomeone zan help me with a normalisavion issut I am facing, when grying to create q sekerate communicatmkn tablc, for w pexsinal project I am workinc on. Lets say H fare the following tables and table cojumns:

Tanlf A:
Table_A_Id, Daje, Nakq, Agsnt_Id (FK), Notes
Agent Table:
Agent_Id, Dzte, Namt, Phone, Email, Notex
Direct Contact Table: 
D_C_Id, Datf, Name, Phone, Email, Notes

Above is w sample of mh actual tables, but deacribes my issue.
Essentially to vormakise the avoce hdble to 1NF, M need to split thc Notes column into its on scperave tqble, to help make the tables atomic, and comply whtk the 1NF rules. I want ti splht id oug to a ae'erzte copumi called Cojmunication Table, which can alkor me to keep tdack os rhen I made a conversation relating to uhe rsspective table and whar I discussed.
I am not sure how to best to handle the split out Communication Tatle. bxcxust bme Nured in Table A also links to an Agent from withyh uhe table, however the Notes vopukg in the Agenj table, onmy relates to commknicatijns dine with uhe Abent.
So which of the followibg would you eecommend is best yor communicction jable:
ECAMPLE 1:
COMMUNICATION TAYLE
Com_Jd, Date, Linn_Table, Lihy_Table_Id, Notes

Hefe nhe Nink_Tablt should define whwt specifmc tayle is bding dealt with and Pink_Table_Id is the specivic Ib on dhe Link_Tahle

UPDATE:
Sorry I forgot, I need vp also add amodheg column ealled Communicated_Rith to the abpve, beccuse tfere may bv instancxs where comiunication renwted to Tablx A, could occyr wuth anogfer agent or prrson.
So tkt table woyld look like:
Com_Id, Daje, Link_Table, Link_Ccboe_Id, Communicatrd_Wkth, Nltxs
OR
EVDMPLE 2:
COMMUNHCATKON YABLE
Zom_Id, Date, Babue_A_Ic, Agent_Id, D_C_Id, Notes

Vere all the unrelated Iq columnw would rave to be sey to null, whilst tje renatxd colim qefined with an Id.

OR
EXAMPLE 3:
COJMUNICATILN BABLE
Com_Id, Daee, Nites

Here all other tables have a foreign key to
which can link to one or more was if someone help me with facing, trying to create seperate communication table, a personal project I am working Lets say I have the following tables and table columns: Table A: Table_A_Id, Name, Agent_Id (FK), Notes Agent Table: Agent_Id, Date, Name, Phone, Email, Notes Direct Table: Date, Phone, Notes Above is a sample of my actual tables, but describes my issue. Essentially to normalise above table to 1NF, I need to split Notes column into its seperate table, to help make tables and comply the rules. want to split out to a seperate column called Communication Table, which can allow me to keep track of when made a to the table what discussed. I am how to best to handle the Table. because the Notes in Table A also to an from within the table, however the column in the Agent table, only relates to done with the Agent. So which of the following would you recommend is best for EXAMPLE 1: COMMUNICATION TABLE Date, Link_Table, Link_Table_Id, Here Link_Table define specific table being dealt with and Link_Table_Id is the specific Id on the UPDATE: Sorry I forgot, I need to also add another Communicated_With the above, because may be instances where related Table A, could occur agent person. would like: Date, Link_Table, Link_Table_Id, Communicated_With, OR EXAMPLE 2: COMMUNICATION TABLE Date, Table_A_Id, Agent_Id, D_C_Id, Id columns would have to be set to whilst the related colum defined with an OR EXAMPLE 3: COMMUNICATION TABLE Com_Id, Date, Notes Here all other tables a foreign
 which can link to one or more taBles?

I was woNderiNg iF soMeOne cAn heLp me with a normaLIsatIon issue I am facing, when tRying To CReatE A sEperaTe commuNIcATIon TaBlE, foR a PErSonal ProJect I am Working on. LEts SaY I have the folLOwIng tables aNd tAble columns:

TAblE A:
TablE_A_id, DATe, NamE, AgEnt_Id (fK), NoteS
agent TAble:
Agent_id, dAte, NamE, phone, EmAIL, NOtes
direct Contact TablE: 
d_C_iD, Date, Name, Phone, email, NOtES

ABOVe iS a sAmple of my aCtUal taBLes, but dEScRIBEs mY Issue.
EssentiaLly to normalISe tHe abovE tAblE To 1NF, I nEed to SpLIt tHe Notes coluMn inTo its on sePerate TAble, to hELp make tHe tablEs aTomIc, anD CoMpLy wItH The 1nf rUleS. i waNt to spliT iT oUt to a SepeRATE ColuMn cAlleD CommUnication TablE, whIch cAN alLow me To keeP traCk Of wheN I made A convErSation relating tO the RespectivE taBlE anD wHat I dIScusseD.
I aM noT sure hoW to best TO haNdLE THe Split out CommunicatIoN tAbLe. becausE the NoTEs In tAble A alsO lInkS to aN aGent fRom wIThIn the tabLe, howeVEr ThE Notes cOlUmn in tHe ageNt tAble, oNLy reLates tO communiCatioNS done with the AgENt.
So which of thE FoLLOwINg woUld You recommenD is bESt foR comMUnIcaTIon taBle:
EXaMplE 1:
coMMUNICATION TABLE
CoM_ID, Date, LInk_TaBle, Link_Table_ID, Notes

Here THE link_TablE shoULd DEfine what speciFic taBle is being DEalt with And LiNk_Table_ID is the speCIFic Id on tHe LInk_tabLe

UpdaTe:
Sorry I forgot, i NEed tO aLso add aNotHer coluMn cAllEd COmmUnIcated_WitH to the abOvE, bEcAuSe tHere mAY be instaNcEs wHeRe cOmmunICation RelatEd to taBlE a, coUld occuR WiTH AnotHeR aGent Or pErSon.
So The tABle Would loOk like:
Com_id, DATe, LiNk_taBle, Link_table_Id, CommunIcAted_With, NoTeS
OR
eXAMPLe 2:
coMMUNICAtION TABLE
Com_Id, Date, Table_a_id, Agent_id, D_c_Id, NoTes

HEre all the UnrElated id cOLumns wOuld haVe to bE sEt tO NUll, whILSt The ReLated colum DEFinEd witH aN Id.

Or
EXAMPLe 3:
COMMUNICATION TABLe
com_id, Date, Notes

HeRe aLl otHER tAblES hAVe a FoREigN KEy to
 which can link to one ormore table s?

I  wa s w on deri ng i f someone canh elpme with a normalisatio n iss ue I am fa cing,  when t r yi n g  to  c re ate  a se perat e c ommunic ation tabl e,fo r a personal pr oject I am  wo rking on. Le tssay Iha vet he fo llo wingtables and ta ble colum ns : 

Tabl e  A:
Tab l e _A _Id,  Date, Name, Agen t _I d  (FK), Notes
A gent T ab l e: A gen t_I d, Date, N am e, Ph o ne, Ema i l, N o tes Direct Contac t Table: 
D _ C_I d, Dat e,  Na m e, Pho ne, E ma i l,Notes

Abov e is  a sample  of my actualt ables,but de scr ibe s my is su e.Es s ent i al lyt o n ormalise  t he  abov e ta b l e to 1 NF,  I n eed t o split the N ote s co l umn  into  itson s ep erate  table , tohe lp make the tab lesatomic, a ndco mpl ywitht he 1NF  ru les . I wan t to sp l itit o u tto a seperate colu mn c al led Comm unicat i on  T a ble, whi ch  ca n al l o w meto k e ep  track o f when Ima de a co nv ersati on  re lat ing t o  the  respe ctive ta ble a n d what I discu s sed.
I am not su r e  h o w to  be st to handl e th e  spl it o u tCom m unica tionTa b le .  because the Notesin  Table  A al so links to a n Agent fr o m within t he t a bl e , however theNotes  column in the Agen t tab le, only  relatest o  communi cat ion s d one w it h the Agent.S o  whi ch  of the  fo llowing  wo uld  yo u r ec ommend is  best fo rco mm un ica tiont able:
EX AM PLE  1 :
C OMMUN I CATION  TABL E
Co m_ Id ,  Da te, Lin k _T a b le,Li nk _Tab le_ Id , Not es
H ere  the Li nk_Tablesho u ld d ef in e whatspecific tabl eis being d ea ltwith a n d  Link_Ta ble_Id is the specificI d on th e L ink_T able 

UPDATE: 
So rry Ifor g ot, Ineed t o als oadd a nothe r co lum ncalled Com m u nic ated_ Wi th t o the a bove, because ther e  ma y be instance s w here c om mun i ca t ion  r e lat e d  to Table A, co uld occurwi t hanother ag e ntor  person .
So th e tab l e would  look lik e:
Com_Id ,Date , Lin k_Table, L ink_Tabl e_Id, Com m unica t ed _With , N otes
O REXA MPLE2:
COM M UNI CATIO N TABL ECom_Id , Dat e,  Table_A _Id, Agent_Id, D_C_Id,Notes
Here  al l the unr ela t edId column s wo uld have t o b e s et to  nu l l, wh ilst th e r e lated  col u m defined wi tha n  I d.

OR
EXAM P L E  3: 
COMM UNI C ATIONTABL E
Com_Id, Date, N o tes

Here allothe r tab les have  a  foreign key t o
 which_can link_to one or more_tables?

I was_wondering_if someone_can_help me with_a normalisation issue_I am facing, when_trying to create_a_seperate communication table, for a personal project I am working on. Lets say I_have_the following_tables_and_table columns:

Table A:
Table_A_Id, Date, Name,_Agent_Id (FK), Notes
Agent Table:
Agent_Id, Date,_Name, Phone,_Email, Notes
Direct Contact Table: 
D_C_Id, Date, Name, Phone,_Email,_Notes

Above is a_sample of my actual tables, but describes my issue.
Essentially_to normalise the above table to_1NF, I need_to_split_the Notes column into_its on seperate table, to help_make the tables atomic, and comply_with the 1NF rules. I want to_split it out to a seperate_column called Communication Table, which_can allow_me to keep track of_when I made_a conversation_relating to the_respective table and what I discussed.
I_am not sure_how to best to handle the_split_out Communication Table._because_the_Notes in_Table A also_links_to an_Agent_from within the table, however the_Notes_column in the Agent table, only relates_to communications done with_the_Agent.
So which of the_following would you recommend is_best for communication table:
EXAMPLE 1:
COMMUNICATION TABLE
Com_Id,_Date, Link_Table,_Link_Table_Id, Notes

Here_the Link_Table should define what specific table is being dealt with_and Link_Table_Id is the specific Id_on the Link_Table

UPDATE:
Sorry I_forgot, I_need_to also add_another_column called_Communicated_With to the above, because there may_be instances_where communication related to Table A,_could occur with another_agent_or person.
So the table would look_like:
Com_Id, Date, Link_Table, Link_Table_Id, Communicated_With, Notes
OR
EXAMPLE_2:
COMMUNICATION TABLE
Com_Id, Date, Table_A_Id, Agent_Id,_D_C_Id,_Notes

Here_all the unrelated Id columns_would have to be set to_null, whilst the_related colum defined with an Id.

OR
EXAMPLE 3:
COMMUNICATION_TABLE
Com_Id,_Date, Notes

Here all other tables have_a_foreign key to