Make a LibreOffice connectivity/sdbc driver that does not use the in-tree ancient Mozilla copy.
The easiest would probably just to access it over ADO (like we do for Microsoft Access files). It needs Jet 4.0, which is bundled with some versions of Windows, but not the most recent ones. But there is a redistributable that we can bundle: "Microsoft Access Database Engine 2010 Redistributable" http://www.microsoft.com/en-us/download/details.aspx?id=13255
To do that, just take inspiration of our drivers for "Microsoft Access" (.mdb) and "Microsoft Access 2007" (.accdb): they just under the hood rewrite the SDBC URL to the right SDBC-ADO URL, possibly set some parameters, and hand off the connection to the SDBC-ADO driver. This would not need *any* mucking with SQL, ADO/Jet handles it all.
The drives are declared in
<node oor:name="sdbc:ado:access:PROVIDER=Microsoft.Jet.OLEDB.4.0;DATA SOURCE=*" oor:op="replace">
<node oor:name="sdbc:ado:access:Provider=Microsoft.ACE.OLEDB.12.0;DATA SOURCE=*" oor:op="replace">
See also dbaccess/source/core/misc/dsntypes.cxx function ODsnTypeCollection::extractHostNamePort
Then the SDBC-ADO driver recognises this ":access:" prefix specially:
connectivity/source/drivers/ado/AConnection.cxx function OConnection::construct:
if ( aDSN.compareToAscii("access:",7) == 0 )
I suggest to introduce an ":outlook:" prefix.
I see several references to
it gives me a blank page right now.
Another path would be to access Outlook directly over COM/... This would need handling the SQL ourselves, like our mork driver does (connectivity/source/drivers/mork)
There are examples (for VBA) there:
David Ostrovsky dixit in http://lists.freedesktop.org/archives/libreoffice/2012-November/040889.html
> I personally think it is a no go to have two different approaches for
> O and OE integration.
> As discussed with Fridrich on LO Congress, i took a look at seamonkey
> way to handle it. They simple open MAPI.DLL
> and use WAB restriction API to access it. Moreover the algorithms and
> the data strucures in mozab
> (and therefore in mork driver) seems to match 1 to 1 to these api.
> So one straightforward way to integrate both O and OE would be to
> borrow these 5 files from seamonkey tree and adapt it for our need.
As remarked by Michael Meeks in http://lists.freedesktop.org/archives/libreoffice/2012-November/040905.html, following that path, probably better to take that code off *latest* Seamonkey or even better Thunderbird rather than copying the ancient thing we have in-tree.
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
So what is the current name for the API?
"Windows Address Book (WAB) API"
"Windows Contacts API"
apparently they make a new one with every windows release?
Adding self to CC if not already on
Migrating Whiteboard tags to Keywords: (easyHack, difficultyInteresting, skillCpp, skillSql)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
This tool brings your expert system directly into your post box. It additionally examines your Outlook contacts and finds new associations for you on LinkedIn. Also, know about a new feature for Outlook mobile app and issue like Reset Outlook Password by visiting here https://www.outlooktechnicalsupportnumbers.com/outlook-password-reset/
Re-evaluating the EasyHack in 2022
This enhancement is still relevant. But things have changed since 2012. I think using Microsoft Jet Database Engine is not the best approach now, as it is currently called a deprecated technology and it does not support 64 bit applications.
(In reply to DavidO from comment #3)
> So what is the current name for the API?
> "Windows Address Book (WAB) API" or "Windows Contacts API"
> apparently they make a new one with every windows release?
As can be read here, "Windows Contacts" is the new application, and API:
"Windows Contacts is a contact manager that is included in Windows Vista, Windows 7, Windows 8, Windows 10, and Windows 11. It replaced but retains most of the functionality of Windows Address Book and worked with Windows Live Mail and the Vista version of Windows Mail."
Also, Microsoft explicitly says that WAB should not be used, and Windows Contacts API should be used instead, for the new applications:
"New applications should not use this set of interfaces. These interfaces exist for backward compatibility with legacy applications. These interfaces will be unavailable in the future.
In Windows Vista, Windows Contacts replaces Windows Address Book (WAB). For more information about this new mechanism for storing and retrieving contact information, see Windows Contacts."
Here, "Programming Windows Contacts" is discussed with many examples:
Programming Windows Contacts