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

Runtime operating with MySQL Server

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

    Runtime operating with MySQL Server

    I have a system running on Alpha Five v11. The developer version which is on the server (where also the MySQL server is running) connects nicely to the MySQL Server over localhost and the app works correctly with active link tables on the Full developer version.

    Next, I installed a runtime on a client machine (without shadowing it for now) and ran the workspace. It did not connect to MySQL Server and throw an error that it could not connect over localhost.

    Since the way Runtimes work has been changing a LOT over the years (previously you needed the Runtime Enterprise version which does not seem to exist anymore), I am wondering if the Runtime+ now can connect to the MySQL database, or do we need some other version of the RT?

    If it should be able to do so, any idea on why it still does not? I am able to open the MySQL database directory from the file explorer on the client machine so I have the rights to that directory. If there is no runtime related issue, my best guess is I have misconfigured the MySQL server instance somehow. I can't find ANY documentation on how to set up a runtime-MySQL Server connection (or any other SQL server connection). Did a forum search, but could not find anything helpful either. Right now, the full dev version connects, so the server is running, but the runtime does not. Should the runtime not connect through the same named connection as defined in the masterdatabase? I can't seem to set any connections in the runtime? Testing the connection on the Full version works, testing the very same connection on the runtime does not.

    Really stuck with this one. Any help really appreciated!

    #2
    Re: Runtime operating with MySQL Server

    Marcel,

    I use MySQL w. active-link tables & the RT no problem. I think your issue is the connection string. I assume on the development copy you are using "localhost" as the host name. That only works on the machine w. MySQL & A5 developer. When the client machine (using the RT) sees "localhost" in the connection string, it's looking locally and naturally can't find the data. In my own case, the RT runs on the server (it's an automated process) and the developer is on a client machine - the opposite of what you are doing. The host name in my case is the server name, not localhost. On the webside, you can define an alias for the connection string (which gets published to the server) which allows you to get around this problem. But in this case, I don't think there is a way to publish an alias for the RT. Try using the server name instead of localhost and that should solve the problem. This assumes that your server can see itself as the server when working locally (i.e. on the server). I assume that it can.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Runtime operating with MySQL Server

      Localhost is a special word when talking networking. Using it in your connection string in lieu of the real hostname is what is causing your problems.

      https://en.wikipedia.org/wiki/Localhost
      Andrew

      Comment


        #4
        Re: Runtime operating with MySQL Server

        Thanks both for responding! At this point I have already lost half of my hair. This is frustrating....
        No documentation to be found.

        At this point, after having struggled with this the whole day, I am that far that I have a working connection string from the client. Not using Localhost of course but a named user that I got an account on MySQL Server.
        I tested the string made on the runtime, and it tested ok with "Success". Well... the success is not that big since the components still throw an error saying that it can't connect to the server.

        So, how am I supposed to tell the runtime that with this component it should use this connection? Or is that even not the problem ? Who knows. I can't tell from the error message. I know there is a connection string, I know it is selected (in the runtime) and I know it tests "Success". So why then does the component not show in the runtime although it does on the full developer version. At this point I am reaching critical exploding temperature so I need to get some dinner and take an hour off and maybe one of you guys have a solution with this new information? That would be great....

        Comment


          #5
          Re: Runtime operating with MySQL Server

          Not using Localhost of course but a named user that I got an account on MySQL Server.
          Marcel, I can't tell from your response what you are using for the "host name". You should use the server name.
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: Runtime operating with MySQL Server

            I used the IP address from the server as the host name, which works. In the end, the connection string works?
            When I open the runtime > Tools > external database connections and open the connection string and test it, this tests "Success" so that should work Peter?

            However, when I open a component somehow it SEEMS that the runtime is not able to tell which connection string to use. Anyway, it uses the wrong one....

            So, does this not all boil down to the question HOW you configure the runtime to use WHICH string? Or am I seeing this wrong? I go from the thought that each runtime (if on separate machines) will need its own connection string <> its own account on the MySQL Server instance? Or not?

            Comment


              #7
              Re: Runtime operating with MySQL Server

              I'm still confused Marcel. If your connection string is named "Horses" and that string uses the server's external ip address, and you components refer to the connection string "Horses", yes, it should work.
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                Re: Runtime operating with MySQL Server

                Indeed, the string does test "Success". However Peter: there are now 2 connection strings. One is defined on the developer version and works there. That seems to be the string that has been created by me whilst executing the "upsize genie". On the client, where the runtime lives, I created connection string number 2. That one tests OK for the runtime. Of course, when you look from either one of the application instances, you will see BOTH strings.

                How would the runtime know what string to use? How does this work with a runtime? I suppose if you have 3 runtimes on 3 different client computers, should not there be 3 connection strings as well? One for every runtime?
                How can you tie any of the connection strings to any of the runtimes?

                This all makes me think we should use only 1 connection string for all of the runtimes in a network rather then one for every runtime. Maybe you need to think of this as "the application" needing a connection string rather than the device?

                I am also confused about this. Furthermore, one would think that a basic thing as the setup would be described somewhere in the documentation. I can't seem to find anything about it.

                Comment


                  #9
                  Re: Runtime operating with MySQL Server

                  From the developer create the connection string. When building your components you assign which connection string to use. The runtime installations will use the connection string assigned to the component. You do not want to use a separate connection string for each runtime.
                  Andrew

                  Comment


                    #10
                    Re: Runtime operating with MySQL Server

                    What Andrew said. You only want one connection string. It should refer to the server. Delete the other. Make sure your components refer to the single conn string. If all your components already refer to a connection string called "Horses", delete the other conn string and modify the horse conn string to point to the server name or ip address.
                    Peter
                    AlphaBase Solutions, LLC

                    [email protected]
                    https://www.alphabasesolutions.com


                    Comment


                      #11
                      Re: Runtime operating with MySQL Server

                      Got it! Indeed, the "pointe" was to have one connection string for the application, instead of one for the device. Now, with only one connection string, everything runs smoothly from both developer version on the server and the runtime on the client.

                      Thank you all for helping out! I appreciate it.

                      Comment


                        #12
                        Re: Runtime operating with MySQL Server

                        Good!

                        Of course, you can have as many connection strings as needed. Just make sure that their is only one connection per (MySQL) database. e.g. We have a large project which has 5-6 MySQL db's. The reason for this is to keep things reasonably organized and keep our sanity w. so many tables. But there is only one conn string per db: 6 dbs = 6 conn stings (not 12!)
                        Peter
                        AlphaBase Solutions, LLC

                        [email protected]
                        https://www.alphabasesolutions.com


                        Comment

                        Working...
                        X