I guess I was more concerned with affecting other things. I didn't want to spend time learning the innards of the control. But you're right, in the end, it was a tweak.



>Yeah, and it was such a minor change.
>
>>Yes it did, thanks.
>>
>>I really didn't want to get into modifying the source for the calendar, but after I thought about it I concluded that since it didn't work the way I wanted that I should just change it.
>>
>>
>>
>>>And did it work?
>>>
>>>>Yes, the source is included. I added an AppointmentId property to the Appointment class.
>>>>
>>>>
>>>>
>>>>>I haven't looked at it in-depth, but can you inherit from the Appointment class and add your own property?
>>>>>
>>>>>Also, does it include source code? If so, you may be able to make their Appointment class a partial class, and then add your own partial class to complement it. I have no idea if that would work though... just an idea.
>>>>>
>>>>>>I'm looking at the calendar control here http://www.codeproject.com/KB/selection/Calendardayview.aspx
>>>>>>
>>>>>>I like the control, except the Appointment class exposes a very limited set of properties. There is a Start datetime, End datetime, and a Title. The problem is that I don't see how to associate a PK from a table to a specific appointment in the calendar.
>>>>>>
>>>>>>It's conceivable that more than one appointment could have the same starting and ending datetime, and the same subject. Or what's more likely is that in a multiuser environment someone could change the dates or title, so I could not reliably depend on any of this data when trying retrieve an appointment.
>>>>>>
>>>>>>When I load the appointments I also return the PK of each appointment, but I don't see any way to associate the PK to it's appointment class. The Tag property is not exposed. Is there any way to add a property at runtime, like as with VFP's AddProperty?
>>>>>>
>>>>>>Thanks