tlhIn`toq, yes I did notice this however I thought that this was just a side effect of my implementation since I am allowing the user unlimited access to press the button as much as they want?

Wouldn’t I be expected to safe guard the abuse of the button (timers > enable/disable the button etc...) or unassigned from the event entirely if I only needed it to run once?

Can I please ask how you would deal with this type of problem?

No one fancy's a crack at this?

Hi Curtis,

Thanks, I didn't really think of doing this with a timer. It’s not something that seems to be mentioned very much in books although now I can see it working it makes sense and pretty easy to implement.

I Think I will change my DB application to auto update using this.

Thanks very much.

I went directly to the application folder in the \AppData\Local\Apps\2.0\... folder and the application works perfectly fine so it looks like its something to do with the 'ClickOnce' process.

Anything to look out for?

Hi, it's just an old data source that's got all kinds of legacy services coming from it. It's due to be scrapped in a few months.


This might be a solution my problem : http://msdn.microsof...y/bb384436.aspx