I’ve actually fallen victim to a stack guard-page corruption caused by the numerous calls to IsBadReadPtr and IsBadWritePtr in MFC. It wasn’t at all obvious that the memory page in question was on the stack and not the heap (it took ages to even discover that the guard page on the stack was corrupted); after all every local variable is on the stack and many such variables are passed “through” MFC. It took many weeks to debug the issue. Anyway, what’s the point of a function succeeding if it’s called with some random pointer and thus can’t access the data it needs to do its job? Don’t validate memory, crash! Then the source of the problem is staring you in the face instead of some problem far removed from the actual source. Steve

What is the HRESULT ? Check additionally with the "dependency walker" whether all dependent dlls are available

That was fast thanks :-)

Leg-pulling? that sucks! Yeah that sucks when you go out with people whom you dont get sync-ed well. I hate to go out with people whom I don't think would completly match my frequency. If I go, the day gets spoiled. I'll get irritated even if they make a little fun out of me. But, If I'm with people I like the most, whatever they say about me or anything, I'd keep laughing. They keep pulling my legs all day but they also see to that I dont fall down.It never hurts that's cool. And give them a rough pull. That's fun. So it's not a matter with "leg-pulling".. but it's with the people who do it ;) find people of your frequency you'll love it then. Best wishes to Rexx[^]

vijay7173 wrote: I am not sure if Xiangyang Liu was talking about swathi's PL. There is an advantage for not being specific, isn't it? :) My .NET Business Application Framework My Home Page