To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100866
                 Issue #|100866
                 Summary|OO.o hangs when Basic IDE content is saved
               Component|Database access
                 Version|OOo 3.1 RC1
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|none
             Assigned to|dbaneedsconfirm
             Reported by|atjensen





------- Additional comments from [email protected] Sun Apr  5 22:55:17 
+0000 2009 -------
This error has been inconsistent under XP and Linux using the earlier DEV builds
- with RC1 there is now a consistent way to cause it.

To reproduce:
Use the attached ODB file, with a Basic library embedded in the file.
MACRO execution is not required to reproduce.
Open the attached ODB file.
Open the Basic IDE and load the basic library in the ODB file.
Edit any procedure - add one or more lines ( blank lines work)
Now click on the Save tool button - quickly - do not hold the mouse button down
TOO long.
OO.o Hangs

Note: 
Edits to a line seem to cause the problem rarely.
Deleting lines cause it more often, but not ever time.
Inserting lines, at least using XP, SP3, cause it every time.
File>Save in the Basic IDE will do it also, but not every time.
Finally - if you just close the basic IDE without saving and then save the ODB
file the error never occurs.

---------------------------------------------------------------------
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]

Reply via email to