On 2014-09-17 09:00 PM, Noel Grandin wrote:
I have figured out a hacky solution to this.
I'll tidy it up and post an RFC patch to gerrit tomorrow.
It's bedtime for me now and I'm tired of debugging over a horribly
laggy connection :-)
RFC patch posted as :
On 2014-09-17 04:36 AM, Lionel Elie Mamane wrote:
Rather than hard-coding a path, I presume our build system has a
variable for the path to the Windows SDK. Also, rather than me (not
having a Microsoft Windows development environment) trying blindly
and relying on tinderboxes to test the
On Wed, Sep 17, 2014 at 08:05:02AM +0200, Noel Grandin wrote:
On 2014-09-17 04:36 AM, Lionel Elie Mamane wrote:
Rather than hard-coding a path, I presume our build system has a
variable for the path to the Windows SDK. Also, rather than me (not
having a Microsoft Windows development
I have figured out a hacky solution to this.
I'll tidy it up and post an RFC patch to gerrit tomorrow.
It's bedtime for me now and I'm tired of debugging over a horribly
laggy connection :-)
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
If you are interested with MS ODBC drivers... I would like to recommend you
the following page: http://blogs.msdn.com/b/sqlnativeclient/
Regards,
Ribert
On Tue, Sep 16, 2014 at 7:11 PM, Robert Antoni Buj i Gelonch
robert@gmail.com wrote:
What odbc driver are you using for Windows?
No driver is not used at build time. The driver used at runtime is
whichever driver the user asks for, usually via a DSN (that is, the
driver that the DSN is for). The MySQL driver to connect to MySQL, one
of the multiple PostgreSQL drivers to connect to PostgreSQL, the DB/2
driver to connect to
