P
pete rowland
I have an issue with the mapi display tables/property sheets. I use these to
display the properties of a MailUser object in my MAPI address book service
provider.
The problem that I have is that support for drop down list boxes appears to
be broken. Code which has worked fine with office 2003 and earlier no longer
functions correctly…
The symptom of the bug is that the render and function as expected, but some
time after the dialog using the display table has been closed outlook crashes
someplace in OLMAPI32.
I’m puzzled as this is real boiler plate code here, and has worked for years
(Yeah, I know.. it could have been wrong for years!). Speaking
programmatically, I support ImailUser::OpenProperty on the mailuser object
for the property pr_details_table. On receiving this call I build the mapi
display table and pass the table view interface back to the caller.. Mapi
then calls again with open property for each of the controls which have an
associated property type pt_object. These calls will include the drop down
list boxes (DDLBX)
Each of the calls of open property on the tag associated with each DDLBXs
and expects me to return a table view as described in msdn etc. All works
fine, the data are correctly rendered etc, but on closing the dialog OL
crashes as described above. My components are not on the call stack at the
time of the crash. I’ve investigated a little further by wrapping the table
view objects (i.e. class wrapper object) and watching the mapi calls coming
into these objects and seen nothing untoward… our interface are released as
but its clear that the OL code calling has changed between the two versions.
Any suggestions?.. or has anyone else encountered this issue? Or is anyone
using these controls successfully.
Pete Rowland
display the properties of a MailUser object in my MAPI address book service
provider.
The problem that I have is that support for drop down list boxes appears to
be broken. Code which has worked fine with office 2003 and earlier no longer
functions correctly…
The symptom of the bug is that the render and function as expected, but some
time after the dialog using the display table has been closed outlook crashes
someplace in OLMAPI32.
I’m puzzled as this is real boiler plate code here, and has worked for years
(Yeah, I know.. it could have been wrong for years!). Speaking
programmatically, I support ImailUser::OpenProperty on the mailuser object
for the property pr_details_table. On receiving this call I build the mapi
display table and pass the table view interface back to the caller.. Mapi
then calls again with open property for each of the controls which have an
associated property type pt_object. These calls will include the drop down
list boxes (DDLBX)
Each of the calls of open property on the tag associated with each DDLBXs
and expects me to return a table view as described in msdn etc. All works
fine, the data are correctly rendered etc, but on closing the dialog OL
crashes as described above. My components are not on the call stack at the
time of the crash. I’ve investigated a little further by wrapping the table
view objects (i.e. class wrapper object) and watching the mapi calls coming
into these objects and seen nothing untoward… our interface are released as
but its clear that the OL code calling has changed between the two versions.
Any suggestions?.. or has anyone else encountered this issue? Or is anyone
using these controls successfully.
Pete Rowland
