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?