[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 User clu changed the following: What|Old value |New value

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 User clu changed the following: What|Old value |New value

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 User mechtilde changed the following: What|Old value |New value

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 --- Additional comments from [EMAIL PROTECTED] Tue Jun 12 06:25:05 + 2007 --- I suppose QUANTEL has own tracing/logging facilities within their driver ... I

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 --- Additional comments from [EMAIL PROTECTED] Tue Jun 12 14:22:41 + 2007 --- Somehow QANTEL was able to see the output of the OOo SQL statement and compared

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 --- Additional comments from [EMAIL PROTECTED] Mon Jun 11 10:18:22 + 2007 --- Hmm - normally I'd say we do not issue such a statement ourself. We use an ODBC

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 --- Additional comments from [EMAIL PROTECTED] Mon Jun 11 15:07:35 + 2007 --- I have turned on tracing (can find no reference to logging...) through the ODBC

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 --- Additional comments from [EMAIL PROTECTED] Mon Jun 11 19:49:51 + 2007 --- (yes, indeed I meant tracing, not logging, sorry) Hmm. Tracing works fine for me

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 --- Additional comments from [EMAIL PROTECTED] Mon Jun 11 20:30:35 + 2007 --- I, too, am befuddled. How might we go about trying to confirm the driver is the

[dba-issues] [Issue 77388] invalid SQL statement gene rated by open office

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77388 Issue #|77388 Summary|invalid SQL statement generated by open office Component|Database access Version|OOo 2.2