Apache OpenOffice (AOO) Bugzilla – Issue 19118
DDE-Link does not work for access via LAN
Last modified: 2013-02-07 22:14:18 UTC
I added some files to reproduce the problem. Because of the absolute links that will only work if you unzip the example file into a path D:\TEMP\oootestfiles so that the last file "texttest2.sxw" will be in D:\TEMP\oootestfiles\DDE_NET_ABSOLUTE_PROBLEM\texttest1\testtext2\ Might be better that you create your own files, I will explain with my path structure. Steps to reproduce: 1. create 3 files D:\TEMP\oootestfiles\DDE_NET_ABSOLUTE_PROBLEM\texttest0.sxw D:\TEMP\oootestfiles\DDE_NET_ABSOLUTE_PROBLEM\texttest1\texttest1.sxw D:\TEMP\....\texttest1\testtext2\texttest2.sxw 2. add to "texttest1.sxw" text "Date: " and actual date with "Insert Fields" 3. add to "texttest2.sxw" text "Time: " and actual time with "Insert Fields" 4. goto "texttest0.sxw", write something like "Date from texttest1: " 5. goto "texttest1.sxw", mark field "date", Cntrl.-v 6. goto "texttest0.sxw" copy field after your text with menu: Edit-PasteSpecial-DDE 7. Set into "texttest0.sxw" a link to time in "texttest2.sxw" in the same way. 8. Close all 3 files and give network permissions "read/write" to all test folders 9. go to another PC in your LAN and open "texttest0.sxw" with "Modify Links" via LAN. expected: "texttest0.sxw" will be opened with actual date and time from other testfiles by dde. actual: errormessage: "D:\.......\DDE_NET_ABSOLUTE_PROBLEM\texttest0.sxw not found" (same for second source file) It seems that this happens because of the absolute link "D:\...." A Network link would look like "\\RAINERSDESKTOP\DDE_TEXT_PRO\testtext2" But should that not work transparent? I tested with files from issue 19100 with relative DDE- links, that works as expected without problems, excepted the special issue 19100 problems, of course ;-) I m no specialist for WIN DDE specifications and so I do not know whether that should work via Network, so UNCONFIRMED. I will install WORD and test LAN - DDE- behaviour again. Rainer
Created attachment 9037 [details] Testfiles, pls read my comment concernign problems!
TM->SBA: Looks more like a writer-apps. - issue with a "link-problem" than a framework problem to me. Please have a look, thanks !
reassigned to jw
reassigend to mru hi michael, i can confirm this behaviour, but i also do not know if this is a ms-os specific problem or not. i think the path should be saved relativ to the document. just have in my mind: two people working on a network share both have different drive letters for this share, the could not work on a document like this from rainer. i set this to new with target OOo later. if i am wrong and this is a ms problem please set this to invalid
MRU->SBA: I am firm with OLE, but not really with DDE. So we need a volunteer for this...
reassigned to es please have a look
ES->FME: as discussed, please have a look. Thanx!
FME->rainerbielefeld: I'm not sure if I understand the problem. If you change the path of the dde source file to \\your_machine\path\to\files everything should work as expected, doesn't it?
Reply to Additional comments from fme Fri Jul 22 07:15:04 -0700 2005: You are right, so it is.
FME->rainerbielefeld: I still do not understand the problem. Let me sum up: You have a document containing DDE links pointing to a resource in your LAN. Because the DDE sources are in your LAN, the DDE link has to contain a network address like "\\your_machine\your\path". This works as expected, so what's the problem?
A very general description of the problem is: "DDE Links created by standard way do not work for document access via network". Network access will be required very often, so links shoud work always via Network That's why links are absolute in a way that can not work via network. Now we have to decide: - should DDE-Links be created relatiev as standard (pls also see issue 19100, and is tat in accordence to DDE-Standards? - or: should OOo inser DDE-hyperlinks like "\\your_machine\your\path" as standard? - or: should OOo be able to transform absolute links "internal" if it sees that access is via network - or: should we add some hints in HELP - pr: .... Result shoud be that we have an easy way to have DDE-access working on stand-alone-PC _and_ vie network
FME->rainerbielefeld: Thank you for your explanation. I'll pass this issue to the user experience team to make a decision. FME->FL: Please have a look.