To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
--- Additional comments from spri...@openoffice.org Thu Aug 13 13:54:46
+ 2009 ---
Appendum to my perivious comment:
This is reported for Ooo Base 3.1.
---
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
--- Additional comments from spri...@openoffice.org Thu Aug 13 13:53:24
+ 2009 ---
Reported
This workaround works is fine without any parameters, but it does n
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
--- Additional comments from mb...@openoffice.org Mon Jan 26 17:44:50 +
2009 ---
Same issue with:
* OO 2.4.1
* com.mysql.jdbc
* MySQL 5.1
* Ubuntu 8.10 client
*
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
User msc changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
--- Additional comments from [EMAIL PROTECTED] Thu Jul 14 05:36:52 -0700
2005 ---
... and GNU/Linux x86.
--
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
--- Additional comments from [EMAIL PROTECTED] Thu Jul 14 05:32:44 -0700
2005 ---
I reproduced that issue on build m113 using PostgreSQL with the Postgresql SDBC
dr
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51380
--- Additional comments from [EMAIL PROTECTED] Wed Jun 29 12:25:54 -0700
2005 ---
I forgot to mention that I'm using ODBC connected to an SQL Server 2000
database.
