<div>
Thanks. <br />
<br />
I think I should add some more information. The SP I call does not return any data, it does some calculations and then writes data to a table. So VB does not have to interpret any return values. The SP calculates a certain value, then reads the troublesome table with certain values to obtain another values, does some more calculations and write the answer to a table on the database. The select statemant has an where clause containing 3 checks (that is - 2 'AND') The problem lies with one of these that it can not find true, BUT only if it is excecuted from VB, not from the Enterprise manager.<br />
<br />
This sounds like a SQL Server problem, but why only if executed from VB.<br />

</div>


Thanks.

I think I should add some more information. The SP I call does not return any data, it does some calculations and then writes data to a table. So VB does not have to interpret any return values. The SP calculates a certain value, then reads the troublesome table with certain values to obtain another values, does some more calculations and write the answer to a table on the database. The select statemant has an where clause containing 3 checks (that is - 2 'AND') The problem lies with one of these that it can not find true, BUT only if it is excecuted from VB, not from the Enterprise manager.

This sounds like a SQL Server problem, but why only if executed from VB.


<div>
<div class="content wysiwyg-content">
Wrote a Stored Procedure in SQL Server 6.5. Run from iSQL/Enterprise Manager - no problem. Call the same SP from VB5. Get funny results. Traced it to reading a specific &nbsp;field in a table. Why this difference?
</div>
</div>


Wrote a Stored Procedure in SQL Server 6.5. Run from iSQL/Enterprise Manager - no problem. Call the same SP from VB5. Get funny results. Traced it to reading a specific  field in a table. Why this difference?

VB5 ODBC SQL Server

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.