Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index

I have a form which holds several fields which are not bound to a database table, but are showing 
data for information purposes only.

Consider the following code snippet.

        oResultSet = oStatement.executeQuery()
        if not isnull(oResultSet)then
                sDiscountFact = oResultSet.getString(1) 
                oDiscountFact = oForm.getByName("discountFact")
              oDiscountFact.TEXT = format(sDiscountFact, sFormatString2)
        end if

If the form has just been opened, the last line returns an error:
"Property or method not found: .TEXT."
If I now change the formatted field to a text box and back again to a formatted field, the problem 
is solved - until the form is closed and opened again.Is this a bug to be fixed soon, or is this a 
more permanent "feature"?

Now I changed the last line with the following:
That produces the same error message:
"Property or method not found: setString."

I have also tried:
As expected, this does not work, because the field is not bound to a database.

Is there any other alternative to display text on an unbound field, one that works correctly all 
the time? The solution to this problem is really important for me. 

Thanks for any suggestions.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.