[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2010-12-02 Thread oj
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 User oj changed the following: What|Old value |New value

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2010-12-02 Thread oj
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 User oj changed the following: What|Old value |New value

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-09-30 Thread fs
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from f...@openoffice.org Wed Sep 30 18:20:18 + 2009 --- fs-sos: ping. As Marc suggested, is it okay for you to close the issue as

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-08-18 Thread msc
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from m...@openoffice.org Tue Aug 18 06:39:58 + 2009 --- msc - sos: So you can't reproduce this anymore, right? Then we can close this

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-07-06 Thread fs
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from f...@openoffice.org Mon Jul 6 07:48:53 + 2009 --- fs-sos: Uhm, being able to read is an advantage, certainly :) Sorry. Okay, let

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-07-06 Thread sos
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from s...@openoffice.org Mon Jul 6 09:55:18 + 2009 --- sos- I know a dump is easy to make, but I can not reproduce this error myself.

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-07-03 Thread sos
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from s...@openoffice.org Fri Jul 3 07:11:25 + 2009 --- sos-fs Frank as i mentioned in my first comment: This problem occurs only when

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-07-02 Thread fs
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from f...@openoffice.org Thu Jul 2 19:14:02 + 2009 --- fs-sos: Would it be possible for you to re-create the problem in a

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-07-02 Thread fs
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from f...@openoffice.org Thu Jul 2 19:15:06 + 2009 --- and, well, such a one-click-reproducibility would also tremendously increase

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-06-15 Thread sos
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 Issue #|102793 Summary|Ambigouos ColumnNaming in Subform WHERE clause Component|Database access

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-06-15 Thread fs
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 User fs changed the following: What|Old value |New value

[dba-issues] [Issue 102793] Ambigouos ColumnNaming in Subform WHERE clause

2009-06-15 Thread sos
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102793 --- Additional comments from s...@openoffice.org Mon Jun 15 12:47:46 + 2009 --- sos fs: Maybe you spoiled me in the past :-)