StackWalk64() It's not quite trivial though - you'll want to read up on the DbgHelp API[^]. Alternately, just call MiniDumpWriteDump()[^], and use a debugger to examine the resulting dump. ---- I just want you to be happy; That's my only little wish...

First of all thanks for the attention. 1) VC 7.0 (2002) 2) Access Violation error 3) Yes I did, In fact when I performe a shared build there is no problem at all. So if I understood right I need to deliver 3 dll files: MFC42.dll MSVCRT.dll MFC7_0.dll DavidR

When I read about the bug last week, dummy me thought they'd already fixed it. However, for controlled data, I don't think it's a problem. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

Jon Hulatt wrote: Windows has an internal "clock" of (from memory) 12.5ms... Close. For Windows 9x/Me, the system clock ticks at 55 ms. For Windows NT, it ticks at 10 ms. This is the best that can be obtained with a non-RTOS system. "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

Thanx,It is interesting. But I am looking also for api so I could redesign the application for my specific use. DavidR

You simply P/Invoke SendMessage. See http://pinvoke.net/default.aspx/user32.SendMessage[^] for the syntax. This is how you would do it (well, one way) in a native C/C++ application (or even in VB6 and below by declaring the SendMessage API. You'll need the HWND to the destination window, but it sounds like you already have it. You'll also most likely need to register your service either as a specific user with local login rights, or as the Local System with the "Allow service to interact with desktop" checked (search this message board using "Search comments" above for a previous reply about how to do this I wrote a day or two ago). Microsoft MVP, Visual C# My Articles