Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Calling stored procedures which has output parameters

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Calling stored procedures which has output parameters

    A few months ago I worked out how to call sql server stored procedures from a web page (with some help). Now I need to call a stored procedure which has some output parameters ie it passes back to the calling software various values. Does anyone know how to specify the parameters in the command line as output parameters? And also how do you get access to the values of these parameters once the stored procedure has run?

  • #2
    Re: Calling stored procedures which has output parameters

    You say you figured out how to do the call?
    Would you mind helping me on that?

    I need to call a microsoft Sql server stored procedure sending parameters.
    I would like to do it as a user defined function.

    Is this possible?

    thanks!

    Comment


    • #3
      Re: Calling stored procedures which has output parameters

      Hi, below is the code lifted straight from some Xbasic. If it's not clear just ask some more questions.
      Tim

      ‘ I use a few session variables to carry data from one page to another.

      dim session.u_asc_num as N
      dim session.u_sql_sp as C ‘I use this one to hold the text that I will pass to SQL to execute the procedure
      dim session.u_db_result as C
      dim session.my_session as N
      dim session.u_cs as C ‘this variable holds the details about my SQL connection string

      dim t as SQL::Connection

      if .not. t.Open(session.u_cs)
      carry out error reporting
      end
      end if

      dim rs as SQL::ResultSet

      ‘ build the text of the sql script required to execute the procedure
      session.u_sql_sp = "EXEC ASSIGN_AST " + session.u_asc_num + "," + session.my_session

      ' Execute stored procedure

      t.Execute(session.u_sql_sp)
      session.u_db_result = t.CallResult.Text
      rs = t.ResultSet

      ‘ go to next page
      response.redirect("aad_C_fdbk_a.a5w")
      end

      Comment


      • #4
        Re: Calling stored procedures which has output parameters

        A few months ago I worked out how to call sql server stored procedures from a web page (with some help). Now I need to call a stored procedure which has some output parameters ie it passes back to the calling software various values. Does anyone know how to specify the parameters in the command line as output parameters? And also how do you get access to the values of these parameters once the stored procedure has run? I use this one to hold the text that I will pass to SQL to execute the procedure.



        __________________
        Chanel Bags
        Gucci Bags
        Replica Handbags

        Comment


        • #5
          Re: Calling stored procedures which has output parameters

          I have exactly the same problem. I can execute the stored procedure as below in interactive but I can't figure out how to retrieve the returned value:

          dim conn as sql::connection

          ?conn.open("::Name::modiloConnection")
          = .T.

          dim args as sql::arguments

          args.Clear()

          ?args.set("TenantId",1)
          = .T.

          ?args.set("SequenceId",2)
          = .T.

          ?args.set("NextNumber",99999999,sql::ArgumentUsage::InputOutputArgument)
          = .T.

          ?conn.Execute("exec NewSequenceNumber :TenantId, :SequenceId, :NextNumber",args)
          = .T.

          ?args.Find("NextNumber")
          = Data = 99999999
          IsNull = .F.
          Name = "nextnumber"
          Usage = 2
          XML = <SQLArgument>
          <Name>nextnumber</Name>
          <Data Type="N">99999999</Data> <------ NO CHANGE
          <IsNull Type="L">0</IsNull>
          <Usage>InputOutput</Usage>
          </SQLArgument>

          /Charles

          Comment

          Working...
          X