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

MySQL stored procedures & A5V8

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

    MySQL stored procedures & A5V8

    I do not yet have something to experiment with but soon I will be asked to to work with a remote MySQL database in which I will need to call a stored procedure using V8 Enterprise. I have searched the documentation and so far have found virtually nothing on this subject. Still, in a post from Richard I found:
    If you need to access the native capabilities of a specific database, simply code your SQL using native syntax and it will be passed directly to the underlying database. Portable SQL also supports named arguments, including stored procedure calls, in native syntax.
    I also found a forum post or two on the subject but need some explanation of what is going on in the examples. Can anyone briefly explain and give a simple example of how one would call a stored procedure? For example, is the call with xbasic or is it all done within SQL syntax and arguments? If the latter, where is that happening in an example and how is V8 passing the whatever is necessary in xbasic code? Presumably, the "procedure" does something on or within the SQL database (maybe an update or a calculation?) that after the call from V8 could in V8 via a passive linked table or??? Please pardon my ignorance here--any insight or help on any of this would be greatly appreciated.

    Also (for Alpha staff), is there any unreleased documentation in the works that would be helpful in this regard that could be shared on an unreleased basis?

    Ray Lyons


    #2
    Re: MySQL stored procedures & A5V8

    Here's an example that might help. This particular procedure inserts a new record into the USERS table.

    Code:
    dim conn as ole::adodb.connection 
    dim rs as ole::adodb.recordset 
    rs.CursorType = 3
    conn.open("Provider=MSDASQL.1;Password=test123;Persist Security Info=True;User ID=APIACCESS1;Data Source=TestDNS")
    sql = "INSERT INTO USERS (" + fldlist + ") VALUES (" + valuelist + ")"
    Success_Flag = rs.open(sql, conn) 
    conn.close()
    The first four lines open up a connection. Your SQL database administrator can probably help you get his all set up.

    The "sql = ..." line does the work. It passes fldlist and valuelist parameters that were built in Xbasic, like this:

    Code:
    fldlist = <<%a%
    USERID
    COMPANYID
    AGENTID
    ...%a%
    There are two basic challenges when doing this, in my experience:

    (1) Getting the connection string right. Bug your SQL administrator for help until you've got it.

    (2) Getting the sql statement correct. Again, the SQL administrator will know exactly what to feed -- after all he (OK, or she) probably wrote the stored procedure. Treat it like a function that needs to be fed exactly what it expects.
    -Steve
    sigpic

    Comment


      #3
      Re: MySQL stored procedures &amp; A5V8

      Originally posted by Steve Workings View Post
      Here's an example that might help. This particular procedure inserts a new record into the USERS table.

      Code:
      dim conn as ole::adodb.connection 
      dim rs as ole::adodb.recordset 
      rs.CursorType = 3
      conn.open("Provider=MSDASQL.1;Password=test123;Persist Security Info=True;User ID=APIACCESS1;Data Source=TestDNS")
      sql = "INSERT INTO USERS (" + fldlist + ") VALUES (" + valuelist + ")"
      Success_Flag = rs.open(sql, conn) 
      conn.close()
      The first four lines open up a connection. Your SQL database administrator can probably help you get his all set up.

      The "sql = ..." line does the work. It passes fldlist and valuelist parameters that were built in Xbasic, like this:

      Code:
      fldlist = <<%a%
      USERID
      COMPANYID
      AGENTID
      ...%a%
      There are two basic challenges when doing this, in my experience:

      (1) Getting the connection string right. Bug your SQL administrator for help until you've got it.

      (2) Getting the sql statement correct. Again, the SQL administrator will know exactly what to feed -- after all he (OK, or she) probably wrote the stored procedure. Treat it like a function that needs to be fed exactly what it expects.
      Okay! This helps. So, I take it that the "INSERT INTO USERS ()" is the name of the stored procedure in the MySQL database (please correct me if this is wrong).

      Thanks Steve. Interestingly, getting the connection string right is right now my biggest problem. The reason I do not yet have anything to experiment with is that I have not been able to connect with either A5V8 or even with a pretty simple program like DBTools. If I ever connect, it sounds like the stored procedure part may be fairly easy.

      Ray

      Comment


        #4
        Re: MySQL stored procedures &amp; A5V8

        My example is a connection to Firebird system. It required me to set up a driver in the Windows ODBC Data Source Administrator (Control Panel / Administrative Tools).

        Can the administrator of your datasource help you with the connection string?
        -Steve
        sigpic

        Comment


          #5
          Re: MySQL stored procedures &amp; A5V8

          Originally posted by Steve Workings View Post
          My example is a connection to Firebird system. It required me to set up a driver in the Windows ODBC Data Source Administrator (Control Panel / Administrative Tools).

          Can the administrator of your datasource help you with the connection string?
          Well, she is trying but so far it is not working. She seemed to think that it should be a snap to at least get connected using DBtools but what she gave me does not work there either. Not sure what the problem may be. I also cannot ping the IP address she gave for the server. She says that is because she has pinging blocked on her firewall--which I have never heard of, so I do not know yet what the problem may be.

          With XP sp2 Would I need a special ODBC driver with V8 just to connect to a remote MySQL database? I was under the impression this would not be necessary. Not that it means much, but I have MySQL server on my machine and have created a DB that I can connect to with V8.

          Ray

          Comment


            #6
            Re: MySQL stored procedures &amp; A5V8

            I dunno Ray - I've only connected to remote databases with the help of the administrators. I know that one of the servers I connect to will only accept my connection from my web server -- it's set up to expect that IP address and no other which means I can't even test it from my desktop.

            If I understand things correctly you shouldn't need to install any driver but I'm the first to tell you that my knowledge on this subject is weak.

            Keep us informed....?
            -Steve
            sigpic

            Comment


              #7
              Re: MySQL stored procedures &amp; A5V8

              Update:

              I still have not worked out the problem of remotely connecting to the MySQL database. However, I do have that database on my local machine now. I was able to add a record, delete a record and update record, but try as I might I could not call a stored procedure. Turns out there was a bug in A5 that will be fixed in the next patch. I have tested the fix with an interim patch and can now successfully call a stored procedure! Please note: unless they put it in with an updated genie, the code the genie generates needs "call" inserted before the stored procedure name. Apparently this is not necessary with MSSQL.

              Many of you are already aware of this kind of thing, but I'll relate it for those not aware: From the time I reported this problem to Alpha Software to the time it was fixed amounted to a mere 2 hours, and add another 2 hours and I had an interim patch fixing the problem. Try getting MS to do anything, much less this kind of incredible service.

              Ray

              Comment

              Working...
              X