Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

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

Using Stored Procedures

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

    Using Stored Procedures

    I looked in the What's new in V9 and have not found any information on how to execute a stored procedure within a firebird sql database or any other.

    Is there any available info on this ?

    #2
    Re: Using Stored Procedures

    I've been running stored procedures against Firebird with version 8. Here's one that I generalized a bit for this example. The fldlist and valuelist variables are, of course, created before this:

    dim conn as ole::adodb.connection
    dim rs as ole::adodb.recordset
    rs.CursorType = 3
    conn.open("MyConnectionStringHere")
    sql = "INSERT INTO USERS (" + fldlist + ") VALUES (" + valuelist + ")"
    Success_Flag = rs.open(sql, conn)
    conn.close()
    -Steve
    sigpic

    Comment


      #3
      Re: Using Stored Procedures

      Also, v8 had (and I am pretty sure v9 does too) a genie that would call a stored procedure. But note that for mysql one had to manually put "call" in front of the name of the stored procedure. The "call" is probably only necessary for mysql.

      Ray

      Comment


        #4
        Re: Using Stored Procedures

        On second thought, I suppose I should have been a bit more specific. I meant there is in V8 an xabasic script genie (same thing for action scripting) under SQL (using AlphaDAO).

        Edit: I was going to put a screen capture in here but I guess I am too ignorant (or lazy) to figure out how to do that. Sorry.

        Comment


          #5
          Re: Using Stored Procedures

          Ok,

          Thanks to you guys, I was able to find the unique code to run a stored procedure in firebird: EXECUTE PROCEDURE and have a local ask variable passed into the procedure to query on the correct information.

          However, in using an ask variable, I am having the dialog box pop up twice....The first time it pops up and I enter in data, it seems to rerun its self with the default entry reset to its initialized value.

          The section in blue is the troubled section. It can be tested independently of the remained of code. Anyone know why it would do this ?

          Source code below:
          '--------------------------------------------------------------------------

          'Date Created: 26-Mar-2008 04:56:56 PM
          'Last Updated: 26-Mar-2008 05:19:42 PM
          'Created By : Mark Liermann
          'Updated By : Mark Liermann

          'Dialog prep: Set prompts and dimension variables
          dim prmpt_title as c
          dim prmpt_prompt as c
          dim prmpt_default as c
          prmpt_title = "VendorID"
          prmpt_prompt = "Enter the Vendor ID to find:"
          prmpt_default = "0"



          'DIM a connection variable to a Firebird database
          DIM cn as SQL::Connection
          dim flagResult as l
          flagResult = cn.open("::Name::FIREBIRD")
          if flagResult = .f. then
          ui_msg_box("Error","Could not connect to database. Error reported was: " + crlf() + cn.CallResult.text)
          end
          end if

          'Specify if you are using Portable SQL syntax, or not
          cn.PortableSQLEnabled = .f.

          'Dim a SQL arguments object, create arguments and set their values
          DIM args as sql::arguments
          args.add("UID",convert_type(a5_eval_expression("=val(ui_get_number(prmpt_title,prmpt_prompt,prmpt_default))",local_variables()),"N"))


          'Execute a stored procedure to select a vendor
          dim sqlStatement as c
          sqlStatement = <<%sql%
          EXECUTE PROCEDURE AP_VENDORS_SELECT :UID
          %sql%

          'Execute the Query
          flagResult = cn.Execute(sqlStatement,args)
          if flagResult = .f. then
          ui_msg_box("Error",cn.CallResult.text)
          cn.close()
          end
          end if
          dim rs as sql::resultset
          rs = cn.ResultSet

          'The sql_resultset_preview() function opens a window showing a table with the results
          'of your query. Show a maximum of 1,000 rows of data
          'Note that the connection object is passed into the sql_resultset_preview() function so
          'that the function can immediately release the resultset, thereby releasing any locks
          'on the database that some databases might have applied.
          sql_resultset_preview(rs,1000,"Preview Query Results",cn)
          'Now, close the connection
          cn.close()

          Comment


            #6
            Re: Using Stored Procedures

            Try setting a variable to = ui_get_number(prmpt_title,prmpt_prompt,prmpt_default)
            farther up in your script and then plug the variable into your arg.add() line.



            Comment


              #7
              Re: Using Stored Procedures

              I should have clarified, but I did that already and then it works fine. I guess I am curious why it repeats when I merge the ask within the sql arg definition..........

              Comment

              Working...
              X