DDE vs OLE

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In order to print to a label printer from Access 2000, I have to use some
functions from the printer manufacturer. I have a choice between OLE and DDE.

These functions are going to take some modification on my part and I really
don't know anything about either. Is one better then the other? How do I
determine which is best?

thanks for your help
BT
 
OLE is a more complete, complex, modern approach, that was designed
to replace DDE as well as do things that DDE couldn't. In particular,
OLE was designed to be able to locate and start the OLE server, and
handle error conditions. DDE can't do that.

All of which means that OLE is more complex and more flaky! But if
it is working, it is generally easier for people to connect it up
to other things, because you generally have more built-in functionality
with OLE.

When comparing a program (like Word or Access) that has both a DDE
interface and an OLE interface, you will often find that you can do
more with the OLE interface, but that Windows uses the simple DDE
interface for simple shortcuts from Windows like 'print', 'open' etc

(david)
 
Thanks for the information. I ended up using both though.

I used OLE for the meat of the task, but even though all the information was
carrying over to the label printer's application, I couldn't get it to print
with OLE. It said the object didn't have the right Properties or Methods. I
played around with other properties and methods and they all returned what
they were supposed to. I ended up using DDE just to print.

Atleast it does what what I wanted it to.

thanks again
BT
 
Back
Top