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


User yutgor changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|CLOSED                    |UNCONFIRMED
--------------------------------------------------------------------------------
              Resolution|INVALID                   |
--------------------------------------------------------------------------------
                 Summary|Base: NULL date import bre|Base: NULL date import bre
                        |aks type recognition & may|aks type recognition & cra
                        | crash OOo 3.3.0 RC3      |shes OOo 3.3.0
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Mon Nov 22 06:07:02 
+0000 2010 -------
@dbaneedsconfirm: Pls. cc some more people beside r4zoli to look at this issue.

@r4zoli: PLEASE!  Pls. don't just say this is invalid!  Wasn't it you who said,
"If I use default settings (line max 10), and press Auto, the Desc recognized
wrongly as Date" & "The Format example is '1900-01-01'"?  You yourself have
already confirmed 2 wrong behaviours this bug manifests & you're now closing the
issue as invalid???  What kind of service is this???  If you have difficulty
understanding what's going on, pls. forward it to your team lead.  We simply
cannot leave such a defect, which may crash OOo in some cases, unaddressed.  If
we do, we're just inviting the public to use MS Office instead.

And pls. specify what *exactly* you could not reproduce: corrupt data, crash, or
both?  For me, I can reproduce everything even in the *latest* build, OOO330m15,
on 32-bit English Windows XP Pro SP3 (as well as in the *latest official* build,
320m19, on Ubuntu 10.10 in Oracle VM VirtualBox 3.2.10 r66523 on 32-bit English
Windows XP Professional SP3--minus the crash since it's a Linux environment). 
Specifically, after clicking 'Auto', manually changing the field type of 'Desc'
to Memo (yes, *Memo*, not Text), & creating the table, when you open the table,
the data in the 'Desc' column are corrupt & OOo comes to a short freeze & then
crashes!  FYI, I'm attaching the crash error report here
(b-crash-import-null_date-report.xml).  OOo appears to crash in getMsFromTime in
dbtoolsmi.dll.  Pls. have someone with the knowledge to look at it.

BTW, have you looked into Issue #11308 yet?  As noted, fixing that will likely
change the behaviour of the current defect such that failure will occur on data
row /x/ instead of /x/+1.

Again, if you're unable to reproduce whatever phenomena, PLEASE forward to
another developer or your team lead for further testing.  Right now only 2
people have tested so far & 1 person can reproduce it in multiple builds &
OS--actually a colleague helped in testing one of the builds/OS so you may even
consider that as 2 people--& 1 can't.  We really cannot say the issue is invalid
w/o having at least one more person to test the case.  So PLEASE ask some more
people to look at it.

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