To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51035
------- Additional comments from [EMAIL PROTECTED] Tue Sep 13 18:13:19 -0700 2005 ------- Hi Oliver, today I was also facing the problem, that only the ELSE-Condition of Conditional Text Fields is being printed in a Mail Merge. Probably this won't happen anymore when os64 is being released soon. Nevertheless I wanted you to ask to again have a look on this issue regarding conditions which use a database field which is not VARCHAR (I use HSQLDB). I tested an INTEGER field and a DATE field which both behaved in a way that I got mistrustful whether your fix covers all ways of using the Conditional Text feature in connection with database fields. 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 bug you were fixing 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. Now the interesting part (at least for me :-)). 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! I don't know whether my information are useful for you or whether they were not nescessary at all. Only knowing that you definitely fixed at least a part of the above mentioned issues but eventually not the issues I attached in this mail, I had the feeling that I should inform you about my experiences. It appeared to me that there is perhaps more work to do. 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]
