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





------- Additional comments from [email protected] Fri May  8 00:10:29 
+0000 2009 -------
The present UI behaviour (up to at least 3.1.x) is that numeric values are
incremented by 1.0 when the mouse is over a numeric cell, and the mouse wheel is
scrolled up. Numbers are decremented by 1.0 when scrolled down. This behaviour
is consistent in tables, queries and forms.

In all versions of MS Access, the effect of a scroll wheel on a table or query
scrolls the grid view up and down to navigate records. There is no difference if
the mouse is over a numeric value or any other type. In older versions of Access
(2003 and before), the effect of the scroll wheel on a database form navigates
the records forwards and backwards. Values in fields can only change if typed
(or cut/paste). Devs: please keep in mind the MS Access UI behaviour for
migrating end-users.

I highly recommend that the default behaviour of a scroll-wheel should *NOT*
change the data *EVER*, since it too easily contaminates numeric data. Number
data should only be typed in (or cut/paste). I see no reason why this was a good
idea in the first place.

This misfeature is dangerous and is why (unfortunately) we still need to keep
buying MS Access for our office. Our data is valuable since it is our business.
I've been checking this feature since 1.x, but is still an issue in 3.1.x. I
would really love to migrate off MS Access to OO.o, but this is a deal breaker.

I can't figure out the "increment value" workaround mentioned before either.

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