DDE in Collabora Office: Read a Linked Document Range with Explicit Conversion Mode
Use Collabora DDE with a server, full file path, and range, understand numeric conversion modes, and distinguish link refresh from a live guaranteed update.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =DDE("soffice";"c:\office\document\data1.ods";"sheet1.A1") is the vendor’s example for reading Sheet1.A1 from another Calc document. The linked file and supported DDE environment must actually be available.
Syntax and required target details
=DDE("Server"; "File"; "Range" [; Mode])
Server names the application; Collabora applications use soffice. File is the complete filename including its path. Range identifies the source data area or supported document section. Mode optionally controls numeric conversion.
| Mode | Documented conversion |
|---|---|
| 0 or omitted | Number format from the Default cell style |
| 1 | Interpret using standard US English format |
| 2 | Retrieve as text without numeric conversion |
A local path here is an illustrative location, not a file prepared or opened during this guide. Do not point the formula at an untrusted file merely to see whether the link works.
Example: a controlled numeric source
On a supported local setup, create the source document at the stated example path and put numeric 42 in Sheet1.A1. Save it. In a second document, enter:
=DDE("soffice";"c:\office\document\data1.ods";"Sheet1.A1";1)
The documentation-based expected linked value is 42, provided the server, path, source range, and link permissions are functioning. This is a reproducible fixture specification, not an observed native result.
Keep the source and receiving documents distinct and label the receiving cell as linked data. A manually typed 42 in the receiving cell would not test DDE.
Refresh is an explicit part of the workflow
The help says changed source contents can change the returned value, but you must reload the spreadsheet or choose Edit → Links to see updated links. Do not assume every source keystroke instantly refreshes every receiver.
For the controlled fixture, changing source A1 from 42 to 57, saving it, and refreshing the receiving link should lead to a documentation-based expected value of 57. No refresh or timing test was performed for this guide.
If a receiving value appears stale, inspect save state and the documented refresh step before changing the formula or overwriting it with a constant.
Advanced example: preserve an identifier as text
Suppose a source cell contains the text identifier 00123. Mode 2 requests text without numeric conversion:
=DDE("soffice";"c:\office\document\data1.ods";"Sheet1.A2";2)
The intended conditional expectation is the identifier text 00123, rather than a numeric reinterpretation as 123. Verify the source really stores text and inspect the result in the target application; this guide does not certify every server-export or formatting detail.
ISTEXT and ISNUMBER are related type checks. Mode 0 depends on Default-style formatting, while Mode 1 explicitly uses US English numeric interpretation, so locale-sensitive punctuation can matter.
Advanced example: a Writer section
The vendor also documents linking a Writer document’s named section. Its example uses server soffice, a full path to motto.odt, and range/section name Today’s motto. The source text must be placed in the first line of that named section and saved.
This is different from a Calc cell address. Do not pass a sheet reference when the source expects a Writer section name. Confirm the source object and its name rather than guessing from visible document text.
Platform, security, and error limits
The source explicitly disallows cross-platform links, giving Windows-to-Linux document linking as an example. It does not establish browser, mobile, or every operating-system deployment’s DDE support. A documented function name alone is insufficient proof that a given environment can open the link.
DDE reads linked external content. Use only trusted documents and review the path before sharing a workbook, since it can expose private folder or document names. Respect application link-security prompts instead of treating them as formatting errors.
The dedicated section does not enumerate exact native errors for unavailable servers, missing files, denied links, or invalid ranges. Troubleshoot the actual server/path/range and refresh state, and preserve the verified source value separately when an audit requires a fixed snapshot.
Availability and verification
The exact function is documented in Collabora Office 26.04 desktop help, retrieved and reviewed on October 17, 2026. This establishes a documentation scope, not the first release that introduced the function or the last version in which it works; those versions and any retirement date remain unestablished. Collabora Online and mobile support are not inferred from desktop help, nor is behavior in another spreadsheet product.
The examples are documentation-based expectations with independent calculations. They have not been executed in Collabora Office. No application screenshot or native error/coercion certification is implied. Formulas use English function names and semicolon argument separators.
References
- Collabora Office 26.04: DDE (checked October 17, 2026).
- Editorial testing standards.