To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54610 Issue #:|54610 Summary:|Wrong evaluation of Conditional Text fields when |using other field type then VARCHAR Component:|Database access Version:|680m122 Platform:|All URL:| OS/Version:|Windows 2000 Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|none Assigned to:|dbaneedsconfirm Reported by:|helgekraak
------- Additional comments from [EMAIL PROTECTED] Wed Sep 14 08:32:48 -0700 2005 ------- Before I come to my main concern, some introductory notes on the use of a normal VARCHAR field as Conditional Text content: Using VARCHAR fields I only experience the ELSE-condition bug (issue 51035) which Oliver Specht has fixed in os64 (when I do a MailMerge). Also I can use EQ, NEQ,.... without problems. When I select a dataset in the datasource and I choose "Daten in Felder" (probably "data in fields" in the english version) also everything works alright. So the ELSE condition bug only happens when you do a MailMerge. The test in the GUI doesn't cause any mistakes. The following things I noticed using a DATE field: Let's assume the date_field is not empty 1. Using IF (date_field NEQ "") THEN (date_field) ELSE "" -> "data in fields" results in an empty field in the document (actually it should be filled) 2. Using IF (date_field NEQ "") THEN "" ELSE date_field -> "data in fields" results in a not correctly filled field (it should be empty) in the document. 3. Using IF (date_field) THEN (date_field) ELSE "" -> "data in fields" results in a correctly filled field in the document. 4. Using IF (date_field EQ "") THEN "" ELSE (date_field) -> "data in fields" results in a correctly filled field in the document. For me it was interesting to see the behaviour of 1. and 3.. - In my version (m122) in the GUI 1. does work with a VARCHAR field (as I also mentioned in my introduction to the VARCHAR fields) but it does not work with a date field. - Using only the field name of the DATE field instead of EQ or NEQ as IF condition does work (see 3.) in the GUI. This behaviour is contrary to the VARCHAR fields. Finally some regards on the INTEGER field (it uses AUTO_INCREMENT and IDENTY): With this field type I experienced the same behaviour like the DATE field showed. But there was one difference when I tested the 3. function from above: Using IF (integer_field) THEN (integer_field) ELSE "" -> "data in fields" results in an empty field in the document and not as in 3. above in a correctly filled field! As you can see the behaviour doesn't real logic. Not only that VARCHAR in comparison to INTEGER / DATE fields show different behaviour regarding above used conditions, also INTEGER fields in comparison to DATE fields again show a different behaviour. I don't know about other field types and the results there but those two should be enough to demonstrate the illogical behaviour of the conditional text fields. Best regards Helge --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
