I have a problem with the method SortTable at the moment.

If I get a SortTable call simply sorting, I pass it onto the Mapi underlying
table object and it sorts fine and returns S_OK.

But if I try to do any form of grouping on this object it fails with
MAPI_E_TOO_COMPLEX, does anyone know what may be wrong with my table object?
Does it understand grouping by default, or do I need to implement my own
grouping?

Ie. order by subject - works fine.
order by subject and grouped by subject (expanded or collapsed) - both fail.

Any Ideas?

Firstly, Extended MAPI questions are better answered in the
win32.programmer.messaging newsgroup.
Secondly, where exactly does that table come from? You don't even say
whether it is an AB table (and most of them have very limited or
non-existent support for grouping) or a message store (which support
grouping a lot better).

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I have a problem with the method SortTable at the moment.

If I get a SortTable call simply sorting, I pass it onto the Mapi
underlying table object and it sorts fine and returns S_OK.

But if I try to do any form of grouping on this object it fails with
MAPI_E_TOO_COMPLEX, does anyone know what may be wrong with my table
object? Does it understand grouping by default, or do I need to implement
my own grouping?

Ie. order by subject - works fine.
order by subject and grouped by subject (expanded or collapsed) - both
fail.

Any Ideas?

Sorry I got a bit ahead of myself there.

This is a 3rd party MessageStore integration, in Extended Mapi and exchange
client extensions.

We use the normal mapi createTable method to get an IID_IMAPITableData.

We then call hrGetView to create a readonly view of this table and then
create a wrapper around this so we can intercept the incoming calls.

Then outlook calls back into our table object to restrict and find/sort the
rows it requires.

Most of the sort calls I do not need to do anything special, so I just pass
it straight onto the underlying table object obtained from this view.

At this point I please look at my first email.

Thanks about the other newsgroup - I didn't even know it existed and I have
been writing in MAPI for a few years now.



"Dmitry Streblechenko" wrote in message
...
Firstly, Extended MAPI questions are better answered in the
win32.programmer.messaging newsgroup.
Secondly, where exactly does that table come from? You don't even say
whether it is an AB table (and most of them have very limited or
non-existent support for grouping) or a message store (which support
grouping a lot better).

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I have a problem with the method SortTable at the moment.

If I get a SortTable call simply sorting, I pass it onto the Mapi
underlying table object and it sorts fine and returns S_OK.

But if I try to do any form of grouping on this object it fails with
MAPI_E_TOO_COMPLEX, does anyone know what may be wrong with my table
object? Does it understand grouping by default, or do I need to implement
my own grouping?

Ie. order by subject - works fine.
order by subject and grouped by subject (expanded or collapsed) - both
fail.

Any Ideas?

The ITableData interface is designed to be used for the attachment and
recipient tables, for everything else you really need to provide your own
implementation of IMAPITable.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
Sorry I got a bit ahead of myself there.

This is a 3rd party MessageStore integration, in Extended Mapi and
exchange client extensions.

We use the normal mapi createTable method to get an IID_IMAPITableData.

We then call hrGetView to create a readonly view of this table and then
create a wrapper around this so we can intercept the incoming calls.

Then outlook calls back into our table object to restrict and find/sort
the rows it requires.

Most of the sort calls I do not need to do anything special, so I just
pass it straight onto the underlying table object obtained from this view.

At this point I please look at my first email.

Thanks about the other newsgroup - I didn't even know it existed and I
have been writing in MAPI for a few years now.



"Dmitry Streblechenko" wrote in message
...
Firstly, Extended MAPI questions are better answered in the
win32.programmer.messaging newsgroup.
Secondly, where exactly does that table come from? You don't even say
whether it is an AB table (and most of them have very limited or
non-existent support for grouping) or a message store (which support
grouping a lot better).

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I have a problem with the method SortTable at the moment.

If I get a SortTable call simply sorting, I pass it onto the Mapi
underlying table object and it sorts fine and returns S_OK.

But if I try to do any form of grouping on this object it fails with
MAPI_E_TOO_COMPLEX, does anyone know what may be wrong with my table
object? Does it understand grouping by default, or do I need to
implement my own grouping?

Ie. order by subject - works fine.
order by subject and grouped by subject (expanded or collapsed) - both
fail.

Any Ideas?

I think I have found a piece of txt, explaing that when groups are collapsed
they are replaced by their groupHeader, and if expanded then there is a
group header followed by the sorted rows equal to the header value.

Are you aware of any futher information on the header format, and I assume
this goes in as a row in the IMapiTable view.
"Dmitry Streblechenko" wrote in message
...
The ITableData interface is designed to be used for the attachment and
recipient tables, for everything else you really need to provide your own
implementation of IMAPITable.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
Sorry I got a bit ahead of myself there.

This is a 3rd party MessageStore integration, in Extended Mapi and
exchange client extensions.

We use the normal mapi createTable method to get an IID_IMAPITableData.

We then call hrGetView to create a readonly view of this table and then
create a wrapper around this so we can intercept the incoming calls.

Then outlook calls back into our table object to restrict and find/sort
the rows it requires.

Most of the sort calls I do not need to do anything special, so I just
pass it straight onto the underlying table object obtained from this
view.

At this point I please look at my first email.

Thanks about the other newsgroup - I didn't even know it existed and I
have been writing in MAPI for a few years now.



"Dmitry Streblechenko" wrote in message
...
Firstly, Extended MAPI questions are better answered in the
win32.programmer.messaging newsgroup.
Secondly, where exactly does that table come from? You don't even say
whether it is an AB table (and most of them have very limited or
non-existent support for grouping) or a message store (which support
grouping a lot better).

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I have a problem with the method SortTable at the moment.

If I get a SortTable call simply sorting, I pass it onto the Mapi
underlying table object and it sorts fine and returns S_OK.

But if I try to do any form of grouping on this object it fails with
MAPI_E_TOO_COMPLEX, does anyone know what may be wrong with my table
object? Does it understand grouping by default, or do I need to
implement my own grouping?

Ie. order by subject - works fine.
order by subject and grouped by subject (expanded or collapsed) - both
fail.

Any Ideas?

That sounds right. You can always try to access the contents table from one
of the MS store providers (such as PST) and see what it does if the same
grouping is requested.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I think I have found a piece of txt, explaing that when groups are
collapsed they are replaced by their groupHeader, and if expanded then
there is a group header followed by the sorted rows equal to the header
value.

Are you aware of any futher information on the header format, and I assume
this goes in as a row in the IMapiTable view.
"Dmitry Streblechenko" wrote in message
...
The ITableData interface is designed to be used for the attachment and
recipient tables, for everything else you really need to provide your own
implementation of IMAPITable.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
Sorry I got a bit ahead of myself there.

This is a 3rd party MessageStore integration, in Extended Mapi and
exchange client extensions.

We use the normal mapi createTable method to get an IID_IMAPITableData.

We then call hrGetView to create a readonly view of this table and then
create a wrapper around this so we can intercept the incoming calls.

Then outlook calls back into our table object to restrict and find/sort
the rows it requires.

Most of the sort calls I do not need to do anything special, so I just
pass it straight onto the underlying table object obtained from this
view.

At this point I please look at my first email.

Thanks about the other newsgroup - I didn't even know it existed and I
have been writing in MAPI for a few years now.



"Dmitry Streblechenko" wrote in message
...
Firstly, Extended MAPI questions are better answered in the
win32.programmer.messaging newsgroup.
Secondly, where exactly does that table come from? You don't even say
whether it is an AB table (and most of them have very limited or
non-existent support for grouping) or a message store (which support
grouping a lot better).

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I have a problem with the method SortTable at the moment.

If I get a SortTable call simply sorting, I pass it onto the Mapi
underlying table object and it sorts fine and returns S_OK.

But if I try to do any form of grouping on this object it fails with
MAPI_E_TOO_COMPLEX, does anyone know what may be wrong with my table
object? Does it understand grouping by default, or do I need to
implement my own grouping?

Ie. order by subject - works fine.
order by subject and grouped by subject (expanded or collapsed) - both
fail.

Any Ideas?