Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-05-22 : 08:06:02
|
| S.Krishnan writes "We are using SQL 6.5 Server with lots of Store Procedures. We have both 16 bit and 32 bit Front end programs using VB 3 and VB 6. VB 3 programs uses DB-Library calls and VB 6 programs uses ADO to do the connectivity.When the Store Proedure is only executed through VB3 programs it is working fine without any problems. When the same store procedure is called through VB6 programs which uses ADO to connect the procedure works but after sometime when the same procedure is executed from VB 3 programs OR even through ISQLW the results are NOT proper, sometime the figure fields shows 0 values. When the same Store Procedure is recompiled without any modification to the code it works fine till such time the same code is executed from ADO.The worst thing is this is not happeing with all Store procedures or even with the procedures which are similar to the procedure which misbehaves. Even when the same procedure is installed at another User location it works fine at the end but some other procedure at that user location starts giving this sort of problem.Can anyone help us what exactly must be going wrong...." |
|
|
JimL
SQL Slinging Yak Ranger
1537 Posts |
Posted - 2003-05-22 : 16:22:55
|
| What you are discribing has me suspicious of access rights to a S.P. I would first take a look at how the ADO is asigning access rights to these S.P.s and their supporting tables or functions.JimUsers <> LogicEdited by - jiml on 05/22/2003 16:24:25 |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-05-22 : 16:47:25
|
| You need to test the stored procedure in Query Analyzer. You need to figure out if anything is wrong with the stored procedure. Based upon your description, it appears that the problem is outside of SQL Server though. It sounds like there is a bug somwhere in the VB code.You should run SQL Trace (I think that was the 6.5 name of the tool) to determine what exactly is being passed to the stored procedure. Once you analyze the results, you should be able to tell who the culprit is (whether it be the VB3 code, VB6 code, or the actual stored procedure).Tara |
|
|
|
|
|
|
Store Procedures gives wrong result after once executed thru ADO connectivity