[dba-issues] [Issue 108225] Database close is incompl ete

2010-02-23 Thread random_man
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108225





--- Additional comments from random_...@openoffice.org Tue Feb 23 21:08:21 
+ 2010 ---
I wasn't trying to shut down OO.  I was trying to close a document.  However, I
worded things very poorly and so obfuscated the issue.  I shall enter a new 
issue.

-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[dba-issues] [Issue 108225] Database close is incompl ete

2010-02-18 Thread fs
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108225


User fs changed the following:

What|Old value |New value

  Status|UNCONFIRMED   |RESOLVED

  Resolution|  |INVALID





--- Additional comments from f...@openoffice.org Thu Feb 18 11:31:34 + 
2010 ---
This is not a bug. Using the close method on a document is not expected to shut
down the application, no matter whether this document was the last opened one or
not. This is the same for database documents and all other document types.

The fact that OOo is shut down when you close the last document by UI (!) is a
mere UI feature, which is not (only) implemented by using the close method of
the document.

So, it's a matter of the wrong API here. If you want to programmatically shut
down OOo, then you need to use XDesktop::terminate:
http://api.openoffice.org/docs/common/ref/com/sun/star/frame/XDesktop.html.

If you want to simulate the UI behavior of automatic closing, then you need to
use the UI API, aka dispatch API. That is, you need to dispatch the
.uno:CloseDoc command into the window where the document lives in. This will
behave /exactly/ as if the user chose File/Close, including automatic shutdown
of OOo.

Resolving issue as invalid.


As for your last comment:
 Please note that this behavior (s process still in process list) also
 exists when sBase is closed via File-exit !!

This pretty much sounds like a different issue, which I cannot reproduce. Simply
opening a database document, and doing File/Exit, exits just fine here. I think
you either have the quickstarter running, which keeps OOo alive, or you did
something with the document which triggered the problem - in which case you
would need to provide more facts (but in a separate issue, please).

-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[dba-issues] [Issue 108225] Database close is incompl ete

2010-02-18 Thread fs
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108225


User fs changed the following:

What|Old value |New value

  Status|RESOLVED  |CLOSED





--- Additional comments from f...@openoffice.org Thu Feb 18 12:27:42 + 
2010 ---
closing

-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[dba-issues] [Issue 108225] Database close is incompl ete

2010-02-17 Thread chrysten
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108225





--- Additional comments from chrys...@openoffice.org Thu Feb 18 02:37:35 
+ 2010 ---
Please note that this behavior (s process still in process list) also exists
when sBase is closed via File-exit !!

-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[dba-issues] [Issue 108225] Database close is incompl ete

2010-01-11 Thread random_man
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108225
 Issue #|108225
 Summary|Database close is incomplete
   Component|Database access
 Version|OOo 3.1.1
Platform|Unknown
 URL|
  OS/Version|Windows 7
  Status|UNCONFIRMED
   Status whiteboard|
Keywords|
  Resolution|
  Issue type|DEFECT
Priority|P3
Subcomponent|none
 Assigned to|dbaneedsconfirm
 Reported by|random_man





--- Additional comments from random_...@openoffice.org Mon Jan 11 16:41:35 
+ 2010 ---
Attempting to close a Base file using a macro contained in it closes the file
but leaves Windows processes Sbase, Soffice.bin, and Soffice.exe all running in
the Task Manager list.  This happens using Basic language and any of

thisdatabasedocument.close(true),
thisdatabasedocument.currentcontroller.frame.close(true)

I suspect the following facts are related but don't know that for certain:

1.  Basic crash (programming error) also leaves these processes running.

2.  Attempting to open a database form contained within the database by using
ThisDatabaseDocument.getbyname(myform).open in a Basic macro called by the
database OPEN event always fails with No database connection exists.  The
macro must first use:
If Not ThisDatabaseDocument.CurrentController.IsConnected Then
  ThisDatabaseDocument.CurrentController.Connect
End If

3.  Attempting to close a database form contained within the database by using
using ThisComponent.Close(true)always fails with Close Veto Exception.  It is
necessary to use ThisComponent.CurrentController.Frame.Close(true) instead.

-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org