To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113631
------- Additional comments from f...@openoffice.org Tue Sep 28 11:28:09 +0000 2010 ------- notes: 1. the issue encountered in the attached OOoLaw....odb doc is indeed completely different from the issue originally fixed. 2. The issue already happens in OOo 3.2.1 3. There is a workaround Because of 1., to not mix different things in one issue, I am going to submit another issue to take care of the problem, and close this one here, again. Because of 2. and 3., we won't have big chances to get an approval for 3.3 for this bug. Instead, I am going to fix this for 3.4. For the workaround: The problem is caused by the fact that "BillingAndTimeTracking.ClientID" is of type Integer, while "ClientDetails.ClientID" is of type BigInt. This triggers the bug. Changing "BillingAndTimeTracking.ClientID" to BigInt, too, makes the problem disappear. (The same should probably be done for other places where ClientID is held, e.g. in "ClientList" table.) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org