Royce Fickling wrote: float* pData = new float[nNumRows,2]; Should this be: float pData = new float[nNumRows][2]; "Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

I do not see any other ones here that look promising. :( "Love people and use things, not love things and use people." - Unknown "The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

Royce Fickling wrote: I thought that if the optional arguments were not passed, the first call to va_arg would return a null, but that is not the case. Yes, that is NOT the case. You'd need to pass a NULL parameter. Mark Salsbery Microsoft MVP - Visual C++ :java:

Chris Maunder wrote: This would be messy. I agree. That is why I have my email address for CP tied to my blackberry ;P When there are truckloads of replies coming in, my blackberry makes me sound very important/busy :-\ "The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon

All the code in the exception handler should be able to execute outside the scope of the try block. One glaringly obvious potential you have is the use of pDataMovement pointer which is initialized in the try block. So if the exception is thrown before then or if the pointer is null your catch block will just throw another exception. Wait, looking again I see that pointer used before it is even declared so I don't know how you get that to compile at all. led mike

I am not seeing any error. It seems to let me edit my email address in both edit controls, but when I click the save button and close the window, it doesn't apply the change. When I come back and check it is still the old email address.

Royce Fickling wrote: This dialog will appear only if the user attempts to shutdown the system if my service is still doing critical processing. I've written many Services down through the years and never even considered doing something like that. I'm not even sure if it makes sense in the larger scheme of things. I'm also not sure it is supported during shutdown because as I stated I would never even consider doing something like that. led mike

Maybe RegisterDeviceNotification[^] / WM_DEVICECHANGE[^] ... Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

Thanks everyone for the help. The AbortShutdown() is what I was looking for. I know about the WM_QUERYENDSESSION message and how to handle it. Originally, I was looking for a way to get around the hidden window in my service, but because I have to interact with my user, I must use it.

Is Visual Source safe registered on your machine? If this is the case then, it is possible the construction of CoClass fails resulting CoCreateInstance returning Class not registered error. See - http://support.microsoft.com/kb/201431 Sohail