fdo#51004: some progress and 10 years old bug pending
Lionel Elie Mamane
lionel at mamane.lu
Fri Oct 19 02:12:09 PDT 2012
On Thu, Oct 18, 2012 at 10:26:29PM +0200, David Ostrovsky wrote:
> Am 17.10.2012 13:24, schrieb Lionel Elie Mamane:
>> On Tue, Oct 16, 2012 at 08:07:53AM +0200, David Ostrovsky wrote:
>>>> But take into considreation that on windows old mozab driver
>>>> still used.
>> Sorry, I didn't follow this story closely. Why?
> Because on windows moz driver is also in charge for accessing O and
> OE address book.
That's maybe a reason for keeping mozab around (for O(E) AB support),
but that shouldn't keep us from implementing Mozilla Address Book
support through mork on Windows, too :)
As to accessing Outlook address book, we can access it over ADO (like
we do for Microsoft Access files). It needs Jet 4.0, but it is bundled
with Microsoft Windows since Me/2000. I see several references to
it gives me a blank page right now.
Or we could access Outlook directly over COM/...; there are examples
(for VBA) there:
All these solutions would not require a "new" driver, we just generate
the correct ADO connect URL and hand it off to the ADO driver (as we
do for .mdb / .accdb files).
As to accessing Outlook express address book,
says one can do that through the Windows Address Book (WAB) API. It
seems to be deprecated (see
). The replacement is Windows Contacts API
that's a venue to explore, too.
This would require an actual driver, that handles the SQL itself, like
mork for Mozilla.
> I see three options here:
> 1/ extract the parser bits from mozilla driver (reverse engineering) or
> 2/ find an alternative parser solution
> and integrate the picked parser implementation in the new mork driver
> 3/ discontinue O and OE address book support (from LO 4?), and wait
> until windows platform
> get non deprecated O/OE native support and then reenable it again.
Or as above use Microsoft's parser :)
More information about the LibreOffice