Sounds like a bug in the OCX, it might be expecting you to call some initialization function first. 0x8000ffff is E_CATASTROPHIC, which is pretty much a catch-all for "something bad happened". Is this your own ocx? If it is, you should be able to step through it in the debugger. If not, I'd still run it in the debugger and look for first-chance exceptions, that would be a good indication of something wrong in the 'Check' method.

ok JIM i go through that Thax for for your explaination

Try this: _Application app; _NameSpace ns; MAPIFolder folderOutbox; _Items itemsMessages; _MailItem mi; long olFolderOutbox((long) 4); COleVariant vtOptional((long) DISP_E_PARAMNOTFOUND, VT_ERROR), vtTrue((short) TRUE); if (app.CreateDispatch("Outlook.Application") == TRUE) { ns = app.GetNamespace("MAPI"); ns.Logon(vtOptional, vtOptional, vtTrue, vtTrue); folderOutbox = ns.GetDefaultFolder(olFolderOutbox); itemsMessages = folderOutbox.GetItems(); mi = itemsMessages.Add(vtOptional); mi.SetTo("global\_com2000@yahoo.com"); mi.SetSubject("Test..."); mi.SetBody("Hi Mapi\\n\\n"); mi.Send(); ns.Logoff(); } "The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

In the book "The C++ Programming Language, 3rd Ed" by Stroustrup, page 246, The fundamental reason is that a copy constructor initializes uninitialized memory, whereas the copy assignment operator must correctly deal with a well-constructed object. Maxwell Chen

Try looking at this: http://www.codeproject.com/dll/data\_seg\_share.asp Mike

Hello, MSDN subscribe download link http://msdn.microsoft.com/subscriptions/downloads/default.asp With Regrads, R.Selvam

Wrap the header file: extern "C" { #include "api.h" } Or just duplicate the declarations you want. If you're writing a C library, it's good form to put the extern "C" *inside* the header file but not every one does it. Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 1.1.5 [^]: A free RSS reader with support for Code Project.

Well what I meant was void FOO(int* p){*p+=1;} int* i = NULL; FOO(i) If you use references then this sort of problem just can not occur. So it is not that an error will be caught at compile time, there can be no error if you use references. Anyway replacing pointers with references is not always feasible, if the concept of null object is valid, or if the pointer must be rebound (references cannot.) I agree and that is what I said.

http://vertigo.hsrl.rutgers.edu/ug/make_help.html[^] More help on Google searches. "It was when I found out I could make mistakes that I knew I was on to something." -Ornette Coleman

Use Michaels's suggestion, or pass a pointer to the second dialog, as in: m_mydlg2.myptrvariable2 = &myvariable1; Now when myptrvariable2 is modified in the second dialog, the first dialog will automatically "see" the change(s). "When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

class A { static int compare( const void *arg1, const void *arg2 ); void SortEm( void ); }; void A::SortEm( void ) { qsort(..., compare); }