Hi Pauly,
I will need to add an option to turn it off. At the moment it's an intrinsic part of how the control works.
>> And all the records that were related to the original date (The day that was dragged) disappear when it's dropped.
Tell me more about this please. What's happening underneath is that your form procedure is being called as if the user opened the form, changed the date, and saved the form. So if something goes wrong with the drag & drop, it would be interesting to know if the same thing goes wrong when the date is changed.
One thing you may not have set (which may be what is causing the grief) is the setting on the Priming tab of the Form. (The form, not the calendar.) On the Priming tab of the form is a setting
From Calendars:
This lets you set the Date field(s) and Time fields. This is what the template uses for the drag & drop.
the UpdateConferences form procedure, in the HotDates example is a good working example.
>> That would be cute if I wanted it, but I dont -
I bet it'd be even cuter if it worked in your app <bg>... It is a pretty cool feature though for folk using the calendar.
cheers
Bruce