Issue 24109 - Opening spreadsheets with DDE link set with "1" parameter fail
Summary: Opening spreadsheets with DDE link set with "1" parameter fail
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: frank
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-05 14:29 UTC by lolomic
Modified: 2013-08-07 15:15 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Example (45.38 KB, application/x-compressed)
2004-01-05 14:35 UTC, lolomic
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description lolomic 2004-01-05 14:29:51 UTC
I'm using OpenOffice 1.1 (french) under Windows 2000 SP4 for one major reason : In Excel, DDE link or NOT working properly with some of my server software. With OO, it works fine. But I'd like to point out what I found to be a weird thing (a bug I think).

Here is the procedure to reproduce the problem :

1.Create or open a new spreadsheet (excel-like document) (« Classeur » in french)
2.In any cell, add the following formula : =DDE("GAPCS";"Measure1";"IB_magnitude_009";1)
3.Save the document under OO format (i.e. XXX.SXC) and close it.
4.Open it, you get an error message saying there is a problem in CONTENT.XML. See below for message. OO then close.
5.To get rid of the problem, create a new document.
6.In any cell, enter the following formula : =DDE("GAPCS";"Measure1";"IB_magnitude_009")
7.Save and close (see enclosed OK.SXC file).
8.Open it : no problem.

The « 1 » parameter at the end of the DDE function is necessary in my application as it not always recognize the DDE information as number (but sometimes, for unknown reason, the value red is either TEXT or NUMBER and shows sometimes in TEXT (but not showing the good information) and couple of seconds after is showing in NUMBER (and then the value shown is ok). Adding this « 1 » parameter is helpful as it then ALWAYS recognize the value as a number and therefore ALWAYS showing the good value.

Setting this parameter to « 2 » shows the good « value » but as text format. And never crash. This is not what I want as I need to do calculation with these kind of cell.

Setting this value to "0" shows the TEXT format value that is a wrong value. And never crash.

I figure out I can use it by traslating the TEXT to NUMBER using a TEXTTONUMBER command or similar name.

To explain a little bit more (if it's usefull) GAPCS is my server, the software I read information from. MEASURE1 is the topic I want to read the valu from and IA_MAGNITUDE_009 is the current wich is coming from my device @9.

The NUMBER value (parameter "1") shows "11.39" Amps wich is correct.
The TEXT value (parameter "0") shows "14550". I don't know how is calculated this value that correspond to 11.39 Amps.
The TEXT value (parameter "2") shows "11.39" Amps wich is correct BUT in text format.

Sorry for all the details but it may be useful for you.

Now, the error message. First in french, next in english translation :

French : 
-----------------------------
Titre de la fenêtre : OpenOffice.org 1.1.0
"Erreur lors du chargement du document file:///C:/Documents%20and%20Settings/sav_on.PCL/Mes%20documents/ko.sxc:
Erreur de lecture.
Erreur de format dans le sous-document content.xml du fichier, position 2,3444 (ligne,colonne).. [Note from me : TWO "." instead of 1]
-----------------------------


English translated :
-----------------------------
Window title : OpenOffice.org 1.1.0
Error during loading of the file document file:///C:/Documents%20and%20Settings/sav_on.PCL/Mes%20documents/ko.sxc:
Reading error.
Format error in the file sub-document content.xml, location 2,3444 (line,column)..
-----------------------------

Of course, the file IS present and NOT hidden, read-only or similar thing. I can still open it using Winzip, I can read the content, etc.

Last thing, I use CRASHREP to send similar information but didn't know at that time I can create an issue here. So you may have this information somewhere else.

That's it for now. Please carry on the GREAT job you've done with OO.

L.
Comment 1 lolomic 2004-01-05 14:35:00 UTC
Created attachment 12279 [details]
Example
Comment 2 oc 2004-01-05 15:32:29 UTC
Hi Sascha,
one4you
Comment 3 thorsten.ziehm 2004-01-05 15:53:40 UTC
This shold be fixed in OOo 1.1.1. So I change the target.
Comment 4 sascha.ballach 2004-01-06 09:19:29 UTC
I take it
Comment 5 daniel.rentz 2004-01-06 13:12:29 UTC
Fix reviewed
Comment 6 sascha.ballach 2004-01-06 13:47:53 UTC
fixed in sab010

changed file: XMLExportDDELinks.cxx
Comment 7 sascha.ballach 2004-01-06 14:24:20 UTC
please verify
Comment 8 frank 2004-01-07 15:04:32 UTC
set to fixed
Comment 9 frank 2004-01-07 16:08:43 UTC
Found fixed on CWS sab010 using windows and Solaris.
Comment 10 sascha.ballach 2004-01-13 12:55:52 UTC
Hi Frank,

please send back after verifying in the master so I can put the changes into OOo
2.0 branch. Please change also the target.

Thanks
Comment 11 frank 2004-01-19 14:01:18 UTC
Verified on Master srx645m25s1-1 using Windows, Solaris and Linux Version.

Frank
Comment 12 sascha.ballach 2004-01-20 13:42:11 UTC
I take it and will also fix it in OOo 2.0
Comment 13 sascha.ballach 2004-02-02 17:04:09 UTC
merged into sab012
Comment 14 sascha.ballach 2004-03-01 17:37:41 UTC
please verify in sab012
Comment 15 frank 2004-10-20 14:53:38 UTC
reset fixed
Comment 16 frank 2004-10-20 15:25:12 UTC
FST: Found fixed in cws sab012  on Linux, Solaris and Windows
Comment 17 frank 2004-11-23 14:39:50 UTC
Found fixed on Master src680m62 using Linux, Solaris and Windows Build