Issue 2871 - crashing form cannot be accessed in edit mode
Summary: crashing form cannot be accessed in edit mode
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: PC Windows 2000
: P5 (lowest) Trivial (vote)
Target Milestone: OOo 2.0
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-17 14:08 UTC by schulten
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description schulten 2002-01-17 14:08:14 UTC 
Hi,

I have a form that crashes after some change in the SQL statement. But this is 
not the problem here. I know what I've changed, but I can't correct the SQL 
statement anymore. Everytime I try to edit the document, SO goes to edit mode, 
tries to load the data and crashes before I can switch to design mode.

Could we please go to edit *and* design mode when the user clicks edit 
document? I consider this a defect, since I'm effectively locked out of my form 
now, which means nothing less than a 'destroyed' form document in the current 
SO version.

Dietrich
Comment 1 Frank Schönheit 2002-01-17 16:17:18 UTC 
The option to externally overwrite the documents "open in design 
mode" state is somewhat expensive (to implement), though I definately 
see the problem here. We already had some small discussion here in-
house about this.
The most interesting question is what the user expects from "edit 
document" and "open document", and if (s)he's aware of the 
differences between a document's edit mode and the alive- or design-
mode of the contained form layer.
We don't have a solution at hand, and if this really turns out to be 
a problem users have, this is surely to be discussed publicly for 
finding the best solution.

I assign this issue to myself because I accept it as a problem which 
needs to be fixed in our area.
Comment 2 Frank Schönheit 2002-01-17 16:19:51 UTC 
accepting the issue ....

Dietrich, forgot to mention:
If you want to access you file:
* extract the XML streams from the zip package
* open the content.xml
* search for an "ApplyFormDesignMode" attribute, change the value from
  "true" to "false"
* re-insert the content.xml into the zip-package
* open the document for editing
The form layer should now be in design instead of alive mode, which 
should give you the possibility to correct the statement.

Yes, it's no solution, not even a workaround for unexperienced users, 
but it may help you with you specific problem :)
Comment 3 Frank Schönheit 2002-12-19 14:35:21 UTC 
setting target milestone to OOo 2.0
Comment 4 marc.neumann 2003-09-25 14:06:00 UTC 
"According to the OpenOffice.org roadmap
(http://tools.openoffice.org/releases) this issue was retargeted to
OOo Later."
Comment 5 Frank Schönheit 2003-10-28 06:59:39 UTC 
removing dependency to issue 21786 (crash tracking). This bug here
does not describe a crash, but a problem you have after some crash
occured.
Comment 6 hans_werner67 2004-02-02 12:50:36 UTC 
change subcomponent to 'none'
Comment 7 Frank Schönheit 2004-12-10 17:05:20 UTC 
With the conceptual changes in OOo 2.0, this is fixed by passing: Nowadays, you
can either "Open" or "Edit" forms. In the latter case, the document is opened
for editing, with design mode switched *on*.
Comment 8 Frank Schönheit 2005-02-17 12:08:18 UTC 
cleaning up my issues - this one is fixed in the latest developer snapshots ...