Issue 18233 - database forms get apparently corrupted
Summary: database forms get apparently corrupted
Status: CLOSED DUPLICATE of issue 11879
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-14 20:17 UTC by khoh64
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description khoh64 2003-08-14 20:17:54 UTC
When you work on a document that contains database forms, switching back and
forth between edit and form mode to check out its function, it often appears
that some of the forms become defunct, meaning they don't show their content
anymore. This seems to happen primarily when a SQL-Query failed, but I'm not
sure about the exact cause. I haven't found any means inside OOo to switch the
forms back on, so when you already saved the document in this state, it will
seem corrupted. However, looking at its xml code, one quickly sees that the
respective forms have gotten a new property:

form:ignore-result="true"

Once you delete this, the form is functional again, leaving me wondering what
sense this property might have had originally...

I think this problem affects all versions of OOo I have tried so far.
Comment 1 Frank Schönheit 2003-08-15 08:19:26 UTC
This pretty much sounds like issue 11879 - but 11879 is already fixed
(as I just verified in RC2).

khoh64, could you please try to nail this down? It's hard to guess
what caused this, so it would be great if you could do some triage and
give us more info, if possible.

"ignore-result" corresponds to the "Add Data only" setting in the
properties of the form - it tells the form to not display any existent
data, so it can be used for data entry only.
Resetting this property should give you back the usual functionality.
Comment 2 khoh64 2003-08-15 11:58:28 UTC
Thanks for the explanation of the 'ignore-result' property, it's
exactly as you said and as described in 11879 and 13548, I'm sorry
that I overlooked all this and stole some of your time...
Indeed, I couldn't reproduce the problem in RC1, so maybe I created
but overlooked it while using an older Version and just stumbled over
it when editing the document in RC1.
I think this one should be closed.
Comment 3 Frank Schönheit 2003-08-15 12:07:30 UTC
/me sighs with relief :)
I was afraid that the problem could have re-incarnated in some special
situation ...

marking this one as duplicate

*** This issue has been marked as a duplicate of 11879 ***
Comment 4 Frank Schönheit 2003-08-15 12:07:52 UTC
closing duplicate
Comment 5 hans_werner67 2004-02-02 12:38:12 UTC
change subcomponent to 'none'