A 2 part question -
First, Appointment has a location string that can be set in code but I do not see anywhere in the create or edit dialogs that this property is used. I assume purpose of the location is to record the physical location of the appointment, like 'conference room' or 'main office', is that correct? If so, where would the user enter and view this information?
Second, my interest in Location is because I want to take it over to do something unusual, and there may be a better way to do this...here's what I want to do:
I would like to implement a traditional appointment scheduler using the built-in features of ScheduleView, but I also want to add to the monthview some non-appointment information in the form of all-day events, for example customer birth dates. These 'special' appointments would not be editable by the user and would not be saved in the same database table. I could use the location property to flag these as 'DOB' so when it come time to save the data I would filter out these form the AppointmentsSource first. However I do not want users to be able to end the location of 'normal' appointments, at least prevent them from entering the magic string 'DOB'.
Would there be any problems with this approach and\or any suggestions or alternatives?
kpg
First, Appointment has a location string that can be set in code but I do not see anywhere in the create or edit dialogs that this property is used. I assume purpose of the location is to record the physical location of the appointment, like 'conference room' or 'main office', is that correct? If so, where would the user enter and view this information?
Second, my interest in Location is because I want to take it over to do something unusual, and there may be a better way to do this...here's what I want to do:
I would like to implement a traditional appointment scheduler using the built-in features of ScheduleView, but I also want to add to the monthview some non-appointment information in the form of all-day events, for example customer birth dates. These 'special' appointments would not be editable by the user and would not be saved in the same database table. I could use the location property to flag these as 'DOB' so when it come time to save the data I would filter out these form the AppointmentsSource first. However I do not want users to be able to end the location of 'normal' appointments, at least prevent them from entering the magic string 'DOB'.
Would there be any problems with this approach and\or any suggestions or alternatives?
kpg