Hi Debi!
Not sure if there is a "best practice" here, but we do find ourselves using something like this a lot...
Checkout the demo of this here...
http://www.youtube.com/watch?v=ZBx9O9hE-wU...and you'll see we use an auto enter calc to push lots of related information into the event's description field, while leaving a section of the field (above "---add notes above this line---") so users can still use it as a notes field. In this example we use Zulu's post-edit script to add the contact ID to the event, and then let the auto-enter calc format the description field.
Here is what that auto-enter calc looks like:
If ( IsEmpty ( Events::_id_Contact ) ; Events::Description ;
//------------------------
Let ( [
sep = "---add notes above this line---" ;
c = Contacts::NameFull_LastFirst ;
co = Contacts::CompanyName ;
a = Contacts::AddressStreet1 & ", " & Contacts::AddressCity & ", " & Contacts::AddressPostCode ;
e = Contacts::Email ;
u = Contacts::URL ;
p = Contacts::Phone ;
n = Substitute ( Left ( Events::Description ; Position ( Events::Description ; sep ; 1 ; 1 ) -1 ) ; "¶¶" ; "" )
] ;
If ( PatternCount ( Events::Description ; sep ) = 0 ; Events::Description ; n )
& ¶ & ¶ & sep & ¶ & ¶ &
List ( c ; co ; a ; e ; u ; p )
& ¶ & ¶ & "Status: " & Contacts::Status
& ¶ & ¶ & "LastContact: " & GetAsText ( ContactLastEvents::DateStart ) & " " & ContactLastEvents::Summary
& ¶ & ¶ & "Notes: " & Contacts::Notes
)
// --------------------
)
Hope that helps,
John