I'll start by naming one of my most hated technologies: DDE (Dynamic Data Exchange)... :mad: That's probably the most crappy technology Microsoft has yet invented. After so many years in the Windows API I still don't get it. What's this about sending Windows messages to other application - couldn't Microsoft have figured out something a little more fancy. I mean, come on, for a communication protocol, Windows Messaging probably isn't the best path to take... The documentation claims that you can use it to "...establish conversations and perform transactions with applications...". So it that like a "MS Transaction Server"-lite? And why are we still sending DDE messages to ProgMan. I thought he died many years ago? The fact that the Windows Explorer still uses DDE, and Internet Explorer uses it to launch some URLs correctly simply makes me really tired. Bjarke Viksoe My code at: www.viksoe.dk/code

To cheer up this forum, I thought we should play a little game. The game is "Name your most hated technology". :) It doesn't have to be a Microsoft technology, but you have probably worked with something in the past that you deemed totally hopeless or just not worthy your programming time. This site is littered with acrnonyms like ActiveX, ATL, COM and MFC. Most of them we enjoy and spend many intimate hours with. But what about that OLE Automation stuff? Remember that... when embedding a picture in Excel was a big thing. Do you remember the struggle to figure out the stuff about sources and containers? Or "Direct Animation" - the *big* Microsoft replacement for FLASH web contents... does anyone actually use this. And was I the only one to write a "QuickView File Viewer" shell extension, only so it could be killed in the next Windows version, 2 years later. I also once looked at writing an OLEDB provider using the "Simple OLE DB Provider" interfaces... I'm pretty convinced that all the C++ samples are there to fool the enemy - this has got to be a hack for Visual Basic to allow them to write anything that would be close to an OLE DB provider. No way that overly-simplified buggy no-functionality interface could be a real COM interface. So don't be shy. Here's a chance to flame your most hated technology... regards bjarke

Yes, you need to load the rtf dll to use... So in your tWinMain()... HINSTANCE hInstRich = ::LoadLibrary(CRichEditCtrl::GetLibraryName()); ... int nRet = Run(lpstrCmdLine, nCmdShow); ... ::FreeLibrary(hInstRich); Use the define in stdafx.h to detemine rtf verion... #define _RICHEDIT_VER 0x0200 Have a look at my website below. Lots of nice WTL samples there. Bjarke Viksoe My code at: www.viksoe.dk/code

No, but there is a free library called ZLIB that will help you. There is also free ActiveX controls around, even one on codeproject called SawZip that will do it. And finally I have a few c++ classes on my web site that could do help you. www.codeproject.com/atl/sawzip.asp www.gzip.org/zlib/ www.viksoe.dk/code (last item in c++ section) Bjarke Viksoe My code at: www.viksoe.dk/code

See http://www.vbpj.com/upload/free/features/vbpj/1999/04apr99/vp0499/vp0499.asp Bjarke Viksoe My code at: http://www.viksoe.dk