Issue 13429

Summary:

Saving Files as pocket excel crashes the data inside the file

Product:

Calc

Reporter:

Unknown <non-migrated>

Component:

code

Assignee:

Joost Andrae <Joost.Andrae>

Status:

CLOSED IRREPRODUCIBLE

QA Contact:

issues@sc <issues>

Severity:

Trivial

Priority:

CC:

issues

Version:

OOo 1.1 Beta

Target Milestone:

---

Hardware:

OS:

Windows XP

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
Corrupt spreadsheet	none
original and correct spreadsheet file	none

Description Unknown 2003-04-14 22:17:30 UTC

After opening a pocket excel file, modifying some data and saving it as a 
pocket excel file again, the data inside the file is getting corrupt. After 
closing and reopening the same file on the PC, other data - e.g. numbers with 
less digits than in the original file on the PDA - is shown in the cells.

Comment 1 frank 2003-04-15 07:43:12 UTC

Hi Joost,

one for you I think.

Frank

Comment 2 Joost Andrae 2003-04-15 08:53:51 UTC

Joost->detli: I cannot reproduce this. Please attach a file to this
issue which crashes the data when exported to PocketExcel.

Comment 3 Unknown 2003-04-15 09:15:42 UTC

Created attachment 5675 [details]
Corrupt spreadsheet

Comment 4 Unknown 2003-04-15 09:16:31 UTC

Created attachment 5676 [details]
original and correct spreadsheet file

Comment 5 Unknown 2003-04-15 09:19:00 UTC

detli-> Joost: I've attached the two files. the file tab_org.pxl is 
the correct file from my PDA. In this file, I deleted the content of 
cell C8 and saved it again as a pocket excel file. The result is file 
tab_corrupt.pxl. After reopening this file it doesn't look like the 
original any more and the content of the several cells is different 
too.

Comment 6 Joost Andrae 2003-05-21 14:08:26 UTC

Joost->detli:

I was able to load both files (they are different) but I wasn't able
to reproduce this behavior (neither in srx644m13 nor in srx645m2, the
upcoming CVS developer tree). I tested it against a real PocketPC 2002
device as well. Please check in a newer build.
As it is not reproducible at all I close this issue