This article was previously published under Q122263
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
3.00 3.00a 3.00bWINDOWSkbusage kbole kbinterop
The following are answers to common questions about OLE, dynamic dataexchange (DDE), and Microsoft Works version 3.0 for Windows.
What is dynamic data exchange?
Dynamic data exchange (DDE) is a Windows mechanism that permits the two-way passing of instructions and data between applications. There are many ways of using DDE, including linking, remote control, and embedding.
What is OLE?
OLE (object linking and embedding) allows users to integrate data from different applications. Object linking allows users to share a single source of data for a particular object. The document contains the name of the file containing the data, along with a picture of the data. When the source is updated, all the documents using the data are updated as well.
With object embedding, one application (referred to as the "source") provides data or an image that will be contained in the document of another application (referred to as the "destination"). The destination application contains the data or graphic image, but does not understand it or have the ability to edit it. It simply displays, prints, and/or plays the embedded item. To edit or update the embedded object, it must be opened in the source application that created it. This occurs automatically when you double-click the item or choose the appropriate edit command while the object is highlighted.
While embedding doesn't allow users to have a single source of data, it does make it easier to integrate applications. An embedded object contains the actual data for the object, the name of the application that created it, and a picture of the data.
Does Works for Windows support DDE?
No. The linking and embedding capability of Works' OLE functionality is related to DDE but is different. In addition, OLE does not support data remote control. This means there is no way to control Works from another Windows application.
How does Works for Windows handle OLE internally?
Works for Windows supports both linking and embedding internally.
Works spreadsheets and charts may be linked to a Word Processor document or a Database form.
The following Works objects can be embedded in a Word Processor document or a Database form:
Clip art from the Microsoft ClipArt Gallery
NOTE: Although the Works Word Processor and Database form are OLE destinations, neither may be used as an OLE source application. Therefore, you cannot link or embed from a Word Processor or Database document into another document.
What Microsoft applications other than internal Works modules will work as OLE servers with Works?
Works for Windows can create a link from any source application that supports OLE 1.0 or 2.0. This includes (but is not limited to):
Microsoft Word for Windows
Is anyone other than Microsoft writing products that take advantage of linking and/or embedding?
Yes. While Microsoft was heavily involved in the formation of OLE, it is an open specification that was developed in cooperation with other leading independent software vendors. OLE is applicable to any graphical application that can create or display information.
kbhowto client server container power point ppt pub wks link embed obj worksheet w_works