Here is an issue...
Im programming an application which accesses a SQL server 2000 sp4 and runs some stored procedures. The code is written in Visual Basic.NET (under visual studio.NET and .NET framework 1.1.*).

The problem is that the stored procedures doesn't work as expected.

I know for sure that they are written well, and that is because I used the Visual Studio.NET built-in "Run procedure" command (under the server explorer>myDB>stored procedures(context menu>Run procedure) ).
And im pritty sure that the code is written good as well (or maybe not!!)
I also used the SQL server 2000 profiler which showed me some differences in the actions sequence. The main difference in my opinion is the "Application Name"... Which is "Microsoft Visual Studio" when I run it from there, and "MS SQLME" when I run the application and it accesses the SQL server from the system as a stand alone application. I've been adviced to check the LocalSystem acount for NT permission, because there is a chance that it is not permitted to write to the disk, unlike the account used by MSdevEnv.

Can anyone explain to me what's going on here??? And what are the steps that I should do to give access to my DB???

Note: The stored procedure return -1, and the profiler shows as if the procedure perfomed a "Rollback"

-1 means there was an error and the transaction has been rollback
Can you post some code so that we can see what you are trying to do in this proc



“I sense many useless updates in you... Useless updates lead to fragmentation... Fragmentation leads to downtime...Downtime leads to suffering..Fragmentation is the path to the darkside.. DBCC INDEXDEFRAG and DBCC DBREINDEX are the force...May the force be with you" -- http://sqlservercode.blogspot.com/