Need to prompt user before navigating away from a page, and perhaps stay on page

I need to check information the user has entered on a page against what I have in my database to see if he is entering duplicate data. It is up to him if he wants to proceed or not. I just need to alert him.

The problem is I don't own the button that he clicks so I can't hook up a javascript confirm to the button click. I am running within vendor code. I have an "override PageLoad()" procedure where I can test what page they're currently on. If they are on page "EditForm.aspx" and would normally navigate to "UserFinish.aspx" without any custom code of mine "interfering", I want to test what they've entered on EditForm.aspx and present them with a popup if they've entered duplicate info, and if they click OK button then proceed to UserFinish but if they click Cancel then stay on EditForm.

I've googled and found some things that might work, but it's usually followed by a caveat saying "do the following, but I don't recommend it", so I just wanted to ask for a way that is recommended. Thanks.

Does it have to be a message box? I've found that trying to work with MessageBoxes are a pain in ASP.NET. I just use hidden buttons and when there's an exception, I show the buttons.

I'm not sure what you mean exactly, but I don't have a page on which to hide any buttons. I just have a C# class that's compiled and the DLL that's created gets put in the deployment, and the vendor code will call it simply because it exists and I've defined a path to it. But the vendor page calls my code. I don't have a page.

Quote:

---

Originally Posted by MMock

I'm not sure what you mean exactly, but I don't have a page on which to hide any buttons. I just have a C# class that's compiled and the DLL that's created gets put in the deployment, and the vendor code will call it simply because it exists and I've defined a path to it. But the vendor page calls my code. I don't have a page.

---

Oh. I see what you mean. Hm... well, wouldn't you just create a method that returns a boolean and then allow them to handle it how they choose?

Quote:

---

Originally Posted by weirddemon

Oh. I see what you mean. Hm... well, wouldn't you just create a method that returns a boolean and then allow them to handle it how they choose?

---

I concur to that.

A server method or a client method?

And returns a boolean to where?

If you use webservice then fix up client method.If you use webserver then fix up a server method.