To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105383





------- Additional comments from voob...@openoffice.org Mon Sep 28 14:40:19 
+0000 2009 -------
Quote: "Assigned shortcuts to procedures CallTerminate and Shutdown_Form. Using
either procedure closes both form and database connection on this machine."

This is encouraging as it seems the problem may not exist for the future 3.2
version. I assume you mean running the shell command from a desktop shortcut, as
that has the same effect as calling the Shutdown_Form macro from a pushbutton
event in a form. In this situation running either of the procedures from a
desktop shortcut would effectively be the same. The Shutdown_Form procedure
effectively calls the CallTerminate procedure (via a windows shell command). The
reason the code is done this way is so that when a pushbutton event is used, by
having a shell command call the CallTerminate procedure (stardesktop.terminate)
you do not get a Windows error (see the hyperlink in my issue description for a
discussion on this).

Quote: "A little different w 3.1.1
- CallTerminate still closes the form and the connection."

I find different here. With Vista the form is closed yet the soffice.bin and
soffice.exe processes remain in the windows task manager. In all previous open
office versions it would have closed these processes (btw I operate without the
quickstarter turned on for various reasons).

Quote: "- Shutdown_Form now only closes the form leaving the connection open and
the JVM running."

This is what I am experiencing. If I use the supplied desktop shortcut to launch
the database form (via the open_Surnames procedure such that the Base UI is not
opened), then when the "close form" pushbutton is used to call the Shutdown_Form
procedure you are left with both the Surnames2.odb.lck file still existing and
the two soffice processes in the taskmanager. If the same pushbutton is used
when the UI is also running, then the lock file does get removed yet the two
soffice processes remain in taskmanager. In previous versions of open office the
lock file and soffice processes would be removed by this method both with and
without the Base UI running.

In any case, it seems from your testing that you have been able to show the
issue in 3.1.1, however the issue may not exist in the future 3.2 version. 

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

Reply via email to