To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=110179
User ttreker changed the following:
What |Old value |New value
================================================================================
Status|CLOSED |UNCONFIRMED
--------------------------------------------------------------------------------
Resolution|INVALID |
--------------------------------------------------------------------------------
------- Additional comments from ttre...@openoffice.org Wed Mar 24 23:06:31
+0000 2010 -------
I have changed my mind and I am going to reopen this issue and contest your
disposition of this report as invalid. Your assessment is incorrect. Having
slept on it and then having spent a lot of time exploring, I know exactly what
happened. So here is my assessment of the problem and its solutions:
Problem Statement:
Wizards don't respond when clicked from any of the task lists.
Work Around Solution:
1) Select either the Table or Query task lists (but *not* the Form or Reporter
task lists).
2) Right click a query or table.
3) Select one of either the Report or Form wizard menu items from this menu.
4) When the wizard dialog comes up, cancel it.
5) Goto any task list and click its wizard. It should come up.
6) Save your Base document.
The permanent bug fix requires escalating this problem report to the development
staff.
If the last support rep had done this, I wouldn't have spent the *countless*
hours looking for the solution. Long before I posted this bug report I searched
for solutions. For me posting bug reports is the last resort.
Further, if this had been labeled as a bug the last time it was discovered and
sent up the chain, undoubtedly the developers of this code base would have seen
what the issue was immediately. They know their code, and the solution to this
bug is probably a one line fix.
This is hours and hours and hours of wheel spinning for countless developers
because you seem to misunderstand the assessment of this problem.
Why should I as a Base community member ever put any effort into providing these
detailed debugging efforts if you discard the results as "user error?"
Let me be perfectly clear. I am on Sun's side here. I tell everybody that I know
to try OOo. I am not trying to win an argument. I am not trying to make anybody
look bad. I appreciate your efforts in this matter. For instance your pointing
me down the development track at the time was a worthy approach given what we
knew at the moment. I am glad it turned out to be unnecessary, but I think you
were correct in your evaluation at that moment. I am not pointing a finger at
you and your efforts, I am simply trying to help make Base come of age.
Anybody that understands rdbms based solutions, and all the available options
today, and who has accurately assessed Base, its external db connectivity
architecture and its integration with HSQLDB knows three things:
1) The foundational integrity of Base and its integration with OOo is robust,
highly professional, and bullet proof.
2) Its current level of usability is extremely weak for all but the most trivial
database applications, unless you are an experienced SQL developer.
3) The foundations for a reasonably clean UI are all in place and just need to
be developed. (e.g. things like drag-and-drop Next and Previous buttons for the
form would be nice. In other words things that an Xcel power user would be
comfortable with would in my opinion rocket Base over the top. It is so close to
being there, it amazes me).
Usability is *exactly* what makes me, for instance, hesitate to steer a small
business owner I know who wants to develop a desktop level db app from Base.
Resolving these kinds of immense time-wasters is paramount. Most people won't
turn in the bug report, and not with the analysis I put into this for you. They
will throw their hands up and call Base junk.
***** Escalate this as a bug ***********************
***** Post the above solution as a workaround ***********
Fix the problem, don't sweep it under the rug!!!
---------------------------------------------------------------------
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
