G
Guest
This question is for Outlook 2003 specifically.
I have a requirement to extend native Appointment form and add couple of
fields on it. It is not possible using design custom form.
Choices I have for above requirement is :
(1) Design tab P-2 using custom form, hide original appoinment tab and ship
this custom oft plus bunch of activex controls to achieve to near-same
usability as native form
(2) Add 2 fields in native outlook form by subclassing it
Second option seems better because it is better usability-wise,
maintenance-wise, deployment-wise, keeping-users-customizations etc.
Question:
-----------
Did you come across details of implementing subclassing.
Basic logic involves Getting hwnd from an appointment inspector and
Replacing the window procedure with your own code ( SetWindowLong ).
I am looking for details/codesnippet of implementing this subclassing.
Appreciate all pointers / code snippets / links.
I have a requirement to extend native Appointment form and add couple of
fields on it. It is not possible using design custom form.
Choices I have for above requirement is :
(1) Design tab P-2 using custom form, hide original appoinment tab and ship
this custom oft plus bunch of activex controls to achieve to near-same
usability as native form
(2) Add 2 fields in native outlook form by subclassing it
Second option seems better because it is better usability-wise,
maintenance-wise, deployment-wise, keeping-users-customizations etc.
Question:
-----------
Did you come across details of implementing subclassing.
Basic logic involves Getting hwnd from an appointment inspector and
Replacing the window procedure with your own code ( SetWindowLong ).
I am looking for details/codesnippet of implementing this subclassing.
Appreciate all pointers / code snippets / links.