Post reply

Stored procedure gives different result when called directly or from vb script

  • May 6, 2009 at 10:32 am

    #208974

    hi,

    here is a thing that bothers me:

    I created a stored procedure that takes 2 strings as input. One is a keyword to search for in different field in different tables. The other an email address.

    When I call the procedure from Query Analyzer I get the expected result as attachment mailed to me.

    When I call the procedure from a vb script I get the mail with attachment but it is emtpy....

    I traced it with profiler and the call is made exactly the same.

    Anyone know what's going on? Is this something from SQL Server, vbs (ADODB.Connection) or maybe in exchange?

    Any help is welcome 🙂

    Cheers, JW

  • May 6, 2009 at 10:38 am

    #989715

    Does the user that run VB has the right to execute store proc? Do you have try ... catch block? If yes, is the error = 0?

    Alex Prusakov

  • May 6, 2009 at 1:39 pm

    #989900

    It sounds as though your proc is sending the email since you receive the message when running the proc directly from query analyzer.

    If you are receiving the email with empty data, it would lead me to believe it is not a permissions issue, as the message is still being sent, therefore the proc is still executing.

    There may be a difference in how your paramters are being passed, which is causing the empty data attachment.

    Do you have any code samples, both vbscript and proc that you can post?

  • May 7, 2009 at 8:07 am

    #990359

    Hi,

    I have solved it by setting a high time out on the ADO connection (300 sec)

    Thanks for the replies anyway, it always helps to view things from a different angle.

    Cheers, JW

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply