However how can i know the details of the error such where it occurs in which line. I need something like i get in sql query analyzer. ------------------------------------ To study, study and only to study

Thanks, however i already solve this problem i use a global table. ------------------------------------ To study, study and only to study

Most of the SQL errors are non-recoverable unless you are writing code to design SQL statements. If you commonly get SQL errors then it is a sign that your application isn't using the SQL server properly. For example if you are adding a username/password to a registration database and the username must be unique, you should send a statement that returns different results based on a transacted exist/insert statement rather then trap the exception. Common occurances shouldn't typically appear in error handling or catch blocks. I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon

However if i don'et use dataset, i'm developing only db i don't care what hapen in the application layer. What i should do do delete relevant rows and insert after this or to do some manipulation with data to understand what chenged and aafter this to insert o to delete or to update some rows???? ------------------------------------ To study, study and only to study

Reflection means to examine an object to find out it's properties and methods, then to call them. Whenever you need to. Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer

thanks i got it, I have another question to u: i have stored procedure that perform select ... from .... also this procedure return value (e.g. return 0) if i call to the sp by EXECUTE i got the result of my sp(result of query.) if i do: DECLARE @res int EXEC @res = My Stored proc PRINT @res i got only what the sp return. how to get the return value and the query result(set result) both? ------------------------------------ To study, study and only to study

Thank u in andvance. ------------------------------------ To study, study and only to study

There are other potential transaction configurations, depending upon the database platform and the method of access. SQL Server runs, by default, in AutoCommit mode although it can be disabled, requiring explicit COMMIT or ROLLBACK calls. Oracle does not run in AutoCommit mode by default (in fact I have never determined if it can; I doubt it). Of course, neither of the above comments really matter if the developer is using a managed data provider, all of which (along with the underlying ODBC and OleDB layers) implement some form of AutoCommit heuristics as far as I know, forcing the behavior to act as you describe. I'm mainly making the distinction between exec'ing SQL at the command line versus through a managed provider, on different DB servers. Have a good weekend. The most exciting phrase to hear in science, the one that heralds the most discoveries, is not 'Eureka!' ('I found it!') but 'That's funny...’

Use @@ERROR in your SQL

i tried it however i never got to catch block with error that severity <=10 .... From russia with love ....

Please avail yourself of the many sources of information on the internet. Look on the MSDN website[^], or just Google 'DAAB Enterprise Library'. There are also probably relevant articles on CodeProject. The most exciting phrase to hear in science, the one that heralds the most discoveries, is not 'Eureka!' ('I found it!') but 'That's funny...’

Shhh... I've got a headache and your shouting doesn't help. My: Blog | Photos | Next SQL Presentation WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More