[dba-issues] [Issue 108524] Database document close c auses close veto exception
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108524 --- Additional comments from random_...@openoffice.org Sun Mar 7 22:34:59 + 2010 --- No, as Issue 09661 shows, closing a database form using ThisComponent.Close(TRUE) does generate a Close Veto exception. This is totally repeatable. That issue also shows that you have to close a database form using ThisDatabaseDocument.FormDocuments.GetByName(form name).Close(True) instead. As it turns out, it's not so easy to get the name of the document model if all you have is ThisComponent, which makes it kind of hard to write reusable code, but hey! Can't have everything. The other issues in this issue were dropped and this issue was closed in favor of issue 090661 because the whole situation was contaminated by having the dang quickstarter turned on by mistake. That unfortnuate feature randomly causes all kinds of crazy behavior. I don't know why this issue is still open. It was previously closed. - 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 109661] Programatic document clos e fails with Close Veto Exception
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109661 Issue #|109661 Summary|Programatic document close fails with Close Veto Excep |tion Component|Database access Version|OOO320m12 Platform|PC URL| OS/Version|All 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 Sat Feb 27 16:45:46 + 2010 --- Using Basic, executing ThisComponent.Close(True) Consistently fails with message Basic Runtime Error An exception occurred Type Com.Sun.Star.Util.CloseVetoException Message: . - 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 109661] Programatic document clos e fails with Close Veto Exception
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109661 --- Additional comments from random_...@openoffice.org Sat Feb 27 16:47:37 + 2010 --- Created an attachment (id=68052) In the attached database: - 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 109661] Programatic document clos e fails with Close Veto Exception
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109661 --- Additional comments from random_...@openoffice.org Sat Feb 27 16:49:55 + 2010 --- The attached database contains an OPEN event macro, a macro invoked by button, and one form containing such a button. 1. Start the DB by double-clicking it 2. Observe the form opens because the OPEN event opens it. 3. Click the button on the form. 4. Observe CLOSE VETO EXCEPTION. - 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 109661] Programatic document clos e fails with Close Veto Exception
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109661 --- Additional comments from random_...@openoffice.org Sun Feb 28 03:33:14 + 2010 --- Thank you very much. I wasted significant hours on this. I agree it's closed. - 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
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 108524] Database document close c auses close veto exception
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108524 User random_man changed the following: What|Old value |New value Summary|ODB macros disabled if sof|Database document close ca |fice.bin already running |uses close veto exception --- Additional comments from random_...@openoffice.org Tue Feb 9 03:16:58 + 2010 --- I don't mind at all. Sorry it took awhile. I downloaded and installed RC5 today. All went normally, but the database I previously attached still has the same problem: closing a form causes CLOSE VETO EXCEPTION. The database I provided causes that each and every time a Basic macro tries to close a form. See original description. We can dispense with the other symptoms. I now believe they were all caused by the OO Quickstarter, which snuck its way back in again after I did a routine reinstall. I just forgot to disable it. Quickstart causes symptoms like that, and all manner of random problems. I always disable it. I changed the title of this report accordingly. - 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 108524] ODB macros disabled if so ffice.bin already running
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108524 --- Additional comments from random_...@openoffice.org Thu Jan 21 19:55:17 + 2010 --- Created an attachment (id=67344) Requested demonstration of issue 108524 - 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 108524] ODB macros disabled if so ffice.bin already running
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=108524 Issue #|108524 Summary|ODB macros disabled if soffice.bin already running Component|Database access Version|OOO310m8 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 Thu Jan 21 01:59:27 + 2010 --- This is perfectly repeatable. Given a .odb file containing one form and one macro that will invoke the form: oDoc = ThisDatabaseDocument.FormDocuments.GetByName(FENTRY_FORM).Open 1. Point the odb OPEN event at the macro that opens the form. 2. Turn off OO Quickstart 3. Locate the database in a nontrusted place (desktop here) 3. Make sure no OO document is running (in Windows, processes soffice.bin and soffice.exe are not on the task list in Task Manager). 4. Execute the odb by double-clicking it. 5. Observe the db opens, you must enable macros, and then the db opens the form. 6. Close the form and the database. 7. Open any OO document (so that soffice.bin and soffoce.exe processes are running as shown in Task Manager) 8. While that document is still open, execute the db by double-clicking it. 9. Note that you are not asked to enable macros, the OPEN event does not trigger the macro, and the form does not open. You can repeat the whole scenario by opening the db from openoffice.exe, choosing database, and selecting this database, but you will get the same result. You can relocate the database to a trusted place and you will get the same thing. I conclude that the OO open mechanism is broken. - 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
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
