[libreoffice-users] Re: LO Base 3.4.3 on Linux using ODBC
Le 17/09/11 22:14, Heinrich Stoellinger a écrit : > Hello Alex, > Seems like I unfortunately cannot get rid of the Java Runtime environment. > The reason is that the report-generator needs it!!! :( > Regards > Heinrich Yes, absolutely, the Oracle Report Builder is Java based. Without Java it simply won't run. Alex -- For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: LO Base 3.4.3 on Linux using ODBC
Hello Alex, Seems like I unfortunately cannot get rid of the Java Runtime environment. The reason is that the report-generator needs it!!! :( Regards Heinrich On Sat, 17 Sep 2011 17:50:19 +0200, Alexander Thurgood wrote: Le 16/09/11 20:44, Heinrich Stoellinger a écrit : Hi Heinrich, When I enter data into a table where some columns have a default value defined (i.e., I do NOT actually enter ANYTHING into such colums but rely on the default value) this default value is actually entered correctly into the table. However, the default value is not shown on completion of data entry. Only when selecting the tuple afterwards do I see that everything is o.k. This only happens on my Linux system. LO 3.3.4.1 Base on MS-Vista with the native MySQL-Connector does everything correctly. The native connector and the ODBC have limitations which are different (I don't remember where originally they were listed, but they were, probably when the native connector first came out or was in development). Additionally, there is a lot of buggy behaviour in current ODBC implementation with mysql from within OOo/LibO. One of the problems I remember with the ODBC connector is that OOo was unable to completely ask for all of the functionality supported by the driver, and even then, sometimes the driver incorrectly reported back to OOo what it was capable of handling. So there are several possible causes : - new bug introduced with the OOo 3.4.x branch and taken over into the LibO code ; - bug in the ODBC driver itself; - new bug just in the LibO code that affects ODBC connections. Having had problems myself with a proprietary ODBC connector on Mac, and accessing a mysql db via OOo/LibO, I tend to favour the first of the three possibilities I listed. I would report it as a bug and add it to the increasingly long list. Alex -- Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/ -- For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: LO Base 3.4.3 on Linux using ODBC
Le 16/09/11 20:44, Heinrich Stoellinger a écrit : Hi Heinrich, > When I enter data into a table where some columns have a default value > defined > (i.e., I do NOT actually enter ANYTHING into such colums but rely on the > default value) this default value is actually entered correctly into the > table. > However, the default value is not shown on completion of data entry. > Only when selecting > the tuple afterwards do I see that everything is o.k. > This only happens on my Linux system. LO 3.3.4.1 Base on MS-Vista with > the native > MySQL-Connector does everything correctly. The native connector and the ODBC have limitations which are different (I don't remember where originally they were listed, but they were, probably when the native connector first came out or was in development). Additionally, there is a lot of buggy behaviour in current ODBC implementation with mysql from within OOo/LibO. One of the problems I remember with the ODBC connector is that OOo was unable to completely ask for all of the functionality supported by the driver, and even then, sometimes the driver incorrectly reported back to OOo what it was capable of handling. So there are several possible causes : - new bug introduced with the OOo 3.4.x branch and taken over into the LibO code ; - bug in the ODBC driver itself; - new bug just in the LibO code that affects ODBC connections. Having had problems myself with a proprietary ODBC connector on Mac, and accessing a mysql db via OOo/LibO, I tend to favour the first of the three possibilities I listed. I would report it as a bug and add it to the increasingly long list. Alex -- For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
