this error is because you dropped the images you imported to the imageList or maybe because you deleted them or changed their directory or because you deleted the resources file :^)

Have you set validation group setting on all validators and save button? Sounds like the validator is still running on the cancel button which presumably you dont want to happen because the user has pressed cancel so the textbox values wont be used. The validation occurs when focus is taken of off the control to validate. So if you fill in an unvalidated control and then click on save, the validation event only occurs then. This also prevents the buttons click event from occurring and going back to the server. Therefore you must press the button again to continue

Perhaps this[^] article will help? In particular, handle the NavigateError event. /ravi My new year's resolution: 2048 x 1536 Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com

Mertli Ozgur Nevres wrote: System.Diagnostics.Process.Start( "iexplore.exe", As a Firefox user I tell you: Don't - do - this - EVER! :sigh: Starting the link directly is okay on windows, windows will take care of it itself.

It's ok i found a great article here: http://www.codeproject.com/cs/miscctrl/customscrollbar.asp And i solved the problem by the help of this great article. Many thanks to Greg Ellis... :beer: ozgur.nevres

i found the problem. If i make any changes in my application, and build it, it re-creates the user.config file in Application Data folder with default values. can i force the VS to re-create the file with changed values? thanks... ozgur.nevres

Mertli Ozgur Nevres wrote: it is not easy as you say Sure it is! You tell them that your code will be tested and supported when IE7 is released. You can't be held responsible for any performance or stability issues because they're using unstable and unsupported software from another manufacturer that your code depends on. If your customer insists on using it with IE7, they're on their own. You tell them what the terms of support are. They don't get to dictate that to you because, after all, they're not writing the code, you are. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Not that I know of.

David Stone wrote: You could just use Whidbey. Uh huh. For production software? Marc Latest AAL Article My blog Join my forum!

It's hard to see where an error might occur, so you should try debugging that method and seeing on which line the exception is thrown. You should also try stepping through the code (put a breakpoint on the first line of your Closing handler and step into each line. The low reproducability rate might make that a little tedious, but that's the world of software development. You could also use Debug.Assert which may speed up the process a little. Good luck! -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Checkout the Speech Application SDK at http://www.microsoft.com/speech[^]. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

You did call OdbcDataReader.Read before making any calls, didn't you? BTW, it's hard to know what to ask to diagnose the problem because you gave very little information. Perhaps some surrounding code (from getting the OdbcDataReader to closing it) would be more helpful. The problem is most likely not with the immediate statement that throws an exception. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

web.config and global.asax need to be in the root of the web site. try moving those 2 files to the root of the website and see if that helps. - Sage

This happens to me quite a bit.... 1st, make sure in your project properties that the setting to Generate Debug Info is set to true. If it isnt, simply set it to be so an recompile. If it is already true, set it to false, recompile, back to true, recompile. 9/10 that will get my breakpoints working again. Good Luck!

Thank you, i solved the problem. I found an error in my code.