Re: ESE.DLL exported functions

["Jeff Garman [MSFT]"]

There are no supported APIs to access the Exchange databases at the "brick" 
level.  I've included the article link below that helps explain this:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;904845

I know that one section of the article indicates that you"might" be able to 
access the store in a read-only mode but there are some major differences in 
the different implementations of the ESE engine that can get you into some 
real problems.

Although this is a documented API and is very similar to ESE used with 
Exchange, it is not designed for use with Exchange and has 
limitations/differences that can result in problems with the Exchange store. 
I also suspect that the ESE functionality is going to be newer than the 
ESENT functionality since ESE/Exchange is continuing to be updated. I would 
not be surprised if any ESENT based apps that you get to work, fail with 
future releases since we have no commitment to ensure that ESENT works with 
Exchange.


--
-Jeff

"Serjio" <sergya@xxxxxxxxx> wrote in message 
news:1157734376.768318.159380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I try to develop some Exchange utility using ESE.DLL . I use ESE.DLL
> exported functions reference in MSDN:
>                                 msdn.microsoft.com/library/default.asp?url=/library/en-us/ese/ese/extensible_storage_engine_reference.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ese/ese/extensible_storage_engine_reference.asp
> . But there is an undocumented function in ESE.DLL named JetDBUtilities
> . It seems that the most of ESEUTIL functionality is implemented
> through this undocumented function. Could anybody advise me where I can
> find some info about it?
> Thanks in advance.