How to Silence an Activex 's errors
-
Hi, I've got a 3rd party activex control embedded in a dialog App, occassionally the activex generates an unspecified error resulting in a blank error message box, Whilst the errors aren't integral to my main application, And if necessary I can work arround them, The Messagebox is a pain, Anyone know how to silence an activex from doing this, Regardz Colin Davies
-
Hi, I've got a 3rd party activex control embedded in a dialog App, occassionally the activex generates an unspecified error resulting in a blank error message box, Whilst the errors aren't integral to my main application, And if necessary I can work arround them, The Messagebox is a pain, Anyone know how to silence an activex from doing this, Regardz Colin Davies
Geez, talk about a crappy ActiveX control! It just goes ahead and displays error messages when there's a problem and to top it off, the message is blank! I suggest you call these guys up and tell them to send you an improved version. If they refuse, tell them you'll be happy to disclose to the world what a "wonderful" product they have. That may get them going... If you don't want to go that route, then I suggest you look at writing yourself a system-wide Hook DLL. Then when you detect the message box is about to come up, you can close it down quietly. That's one not-so-nice way to do it, but it's the only way I know of. I had to do something similar a couple of years ago and I got a great jump start from an article I found in CodeGuru -- I don't know if CodeProject has anything like it yet. Good luck! Alvaro
-
Geez, talk about a crappy ActiveX control! It just goes ahead and displays error messages when there's a problem and to top it off, the message is blank! I suggest you call these guys up and tell them to send you an improved version. If they refuse, tell them you'll be happy to disclose to the world what a "wonderful" product they have. That may get them going... If you don't want to go that route, then I suggest you look at writing yourself a system-wide Hook DLL. Then when you detect the message box is about to come up, you can close it down quietly. That's one not-so-nice way to do it, but it's the only way I know of. I had to do something similar a couple of years ago and I got a great jump start from an article I found in CodeGuru -- I don't know if CodeProject has anything like it yet. Good luck! Alvaro
Alvaro, the ActiveX is actually a real popular one, on client machines its the swflash.ocx, I bet you have it and unfortunatly its free so I can't hound the makers.
And actually it's my code that causes the errors, I'm asking it for a variable name that doesn't exist in its structure. Unfortunatly if I don't ask I don't know if it exists. I know this sounds illogical.
But there is no way of enumerating the variable structure it appears.
I'll see what I can do with a hook :-)Regardz