Abnormal Behavior of SQL Server 2008 Enterprise Store Procedure

[Lost User]

There is a bug in your code, but no one here can guess what your code is doing.

[jugnu_ad]

Dear Richard MacCutchan I have written in my post that it is running perfectly through code (VB 6) using SQL Server 2000. The problem occurred when i attached 2000 database in 2008 Enterprise.

[Lost User]

You can write anything you like, it proves nothing. And, as I said before, no one here has the remotest chance of guessing what your code is doing.

[Tim Carmichael]

Turn on Profiler and log what is happening when you call the stored procedure directly versus when you call it from VB 6.

[jugnu_ad]

Thanks for your reply When I call The Stored Procedure directly from Sql Server it adds or subtracts stock qty properly, but when i run it through vb6 code it adds or subtracts qty twice. But its not in every execution of SP. I m running my software for 3 to 4 years it never happened like this in SQL Server 2000

[Simon_Whale]

What Tim is trying to suggest 1. Turn on SQL Profiler and start it running against your database 2. execute the stored procedure from the VB application 3. stop the profiler 4. in the results from the profiler you can see what was executed and the values that were passed to the stored procedure http://technet.microsoft.com/en-us/library/ms181091(v=sql.105).aspx[^] you need to be able to prove if it the database at fault or the stored procedure.

Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON

[jugnu_ad]

Thank you Simon for explaining me what Tim has suggested. Let me do what you both have said and let you know. Thanks

[Lost User]

jugnu_ad wrote:

What could be the cause of this abnormal behavior?

VB6. Which existed waaaay before Sql Server 2008. Chances are that most of the code isn't type-safe but late-bound, and VB may be doing all kinds of magic on the background to make it work. Did I mention that VB.NET is available for free?

Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

[Mycroft Holmes]

Sounds like this may be the issue that finally gets him to update/rewrite his app into a current language. Now there will be a whole lot of pressure while he could have started this a decade ago (so speaks the guy still coding in Silverlight :-O ).

Never underestimate the power of human stupidity RAH

[Lost User]

When you state that something isn't working, you need to show us what that 'something' is. I mean you haven't included your SP code here without which we will not be able to figure out what is wrong.

[Tim Carmichael]

While VB 6 may have it issues, I have written and used in production many applications written in VB 6 pulling data from SQL Server without issue. If there is a problem, I suspect it is with the coding, not the underlying foundations.

[Lost User]

Tim Carmichael wrote:

While VB 6 may have it issues, I have written and used in production many applications written in VB 6 pulling data from SQL Server without issue.

Ditto. I never claimed that VB6 has issues with SQL Server - merely that it existed before Sql 2008. VB6 does not know about Sql2k8, and I doubt that new released Sql versions are tested for backward compatibility for a discontinued product.

Tim Carmichael wrote:

I suspect it is with the coding, not the underlying foundations.

I agree with the first part of this statement, and explained how the underlying foundation can cause this.

Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]