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

Problem with upsizing to mysql..."Relation corrupt"

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

    Problem with upsizing to mysql..."Relation corrupt"

    I'm having an issue when trying to upsize to mysql with Alpha Anywhere v12.

    The process seems to complete as expected with no errors however when I attempt to launch the workspace I get the following error:

    SNAG-0291.jpg

    The original application works just fine without error...

    Does anyone have any ideas on A) what this is telling me and B) how I can begin to track down the problem.

    Many thanks for any ideas and suggestions.

    ampapa,

    #2
    Re: Problem with upsizing to mysql..."Relation corrupt"

    A couple of additional question to go along with my original if I may...

    - Does Alpha log and errors or process issues in a log?
    - Why, when upsizing does it create an entirely "new" workspace instead of migrate just the table/tables that are selected?
    - Is it possible manually create the DB link for just a single table within a workspace?

    Hopefully someone has experienced similar problems or has some input, all is welcome.

    Thanks,

    Comment


      #3
      Re: Problem with upsizing to mysql..."Relation corrupt"

      Some suggestions.
      The custjob.set is the cause of the error. Revisit the set relationships. SQL is finniky about foreign keys.
      I don't know of an error log, but I am on V11
      The upsize genie is intended to do just that - create a new w/space
      Yes, you can link just one table to an sql db. I have one app with a web front end and a desktop front end running against SQLSERVER16
      Method. Create a sql table, create a connection, connect and you will see the sql connection squiggle
      I can't remember if you can do it in reverse and I'm on my tablet, so let me know what you are aiming for and I will see if I can create similar.

      Edit. Yes, you can upsize whichever tables you want to MySql and you can create a new database at the same time. The new workspace has to be opened, and will only show the upsized tables in the workspace now.
      If you want a mixture of DBF and SQL in the same workspace, just use the Add Table feature which will bring over the forms as well.
      Last edited by Ted Giles; 04-24-2019, 12:29 PM.
      See our Hybrid Option here;
      https://hybridapps.example-software.com/


      Apologies to anyone I haven't managed to upset yet.
      You are held in a queue and I will get to you soon.

      Comment


        #4
        Re: Problem with upsizing to mysql..."Relation corrupt"

        Really appreciate the post Ted.

        "Yes, you can link just one table to an sql db. I have one app with a web front end and a desktop front end running against SQLSERVER16
        Method. Create a sql table, create a connection, connect and you will see the sql connection squiggle "

        Exactly what I have going on, php frontending one of the tables that needs read/write access.

        I'll give it another go based on your advice.

        Thanks,

        Comment


          #5
          Re: Problem with upsizing to mysql..."Relation corrupt"

          Let me know if you have troubles.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment


            #6
            Re: Problem with upsizing to mysql..."Relation corrupt"

            Ted,

            I'm hoping your still available for questions... slight delay in getting back to this project but as I look for a way to create the link to an external table it just isn't apparent on how to accomplish this task.

            "Method. Create a sql table, create a connection, connect and you will see the sql connection squiggle"


            Trying to follow your example and I'm not seeing this option on any of the menu's. I may also be a little confused... I'm assuming you are using the existing table and jumping from there as opposed to creating a "new" table..? I also am on V11.

            If I'm thinking about this correctly I should be able to "upsize" or create a link to mysql, copy of the existing table, and make it editable. This would essentially leave the entire Alpha5 program in tact and still function as is with now the updates happening in mysql for this 1 specific table. I would then be able to front end that table in PHP... accomplishing my goal.

            So, a little more guidance would be appreciated...

            ampapa,

            Comment


              #7
              Re: Problem with upsizing to mysql..."Relation corrupt"

              I'm on leave for about 10 days thend I will revisit with an example.
              See our Hybrid Option here;
              https://hybridapps.example-software.com/


              Apologies to anyone I haven't managed to upset yet.
              You are held in a queue and I will get to you soon.

              Comment


                #8
                Re: Problem with upsizing to mysql..."Relation corrupt"

                Just a quick follow up on the progress I've made.

                I believe that I found the linking functionality, I was looking in the wrong place, its a right click on the desktop-> create new I may have over complicated that... .

                I've ran into a slight problem and just wanted to confirm my thoughts. When I was testing on a laptop linking a database it ran without issue and I was able to "replace" or save the newly linked database as the same name as the original, that seemed to work fine.

                However, when I attempted the same in PROD I ran into the following error:

                SNAG-0338.jpg

                Have you seen this error before or anyone for that matter??

                Comment


                  #9
                  Re: Problem with upsizing to mysql..."Relation corrupt"

                  Yes that is correct. Runtime hasn't got the facidity.
                  You are atempting to use RT in a Development mode.
                  Try running the second of your two licenses session on the production pc.
                  See our Hybrid Option here;
                  https://hybridapps.example-software.com/


                  Apologies to anyone I haven't managed to upset yet.
                  You are held in a queue and I will get to you soon.

                  Comment


                    #10
                    Re: Problem with upsizing to mysql..."Relation corrupt"

                    Appreciate the response Ted.

                    Trying to figure out how the distributed system works in Alpha..

                    Does Alpha operate in a Host/Client mode? meaning a limited client install connects to a host machine containing all of the data/application files?

                    In this environment it looks like the client has all of the files installed but isn't the "Development" machine? just trying to understand what I'm up against.

                    Thanks,

                    Comment


                      #11
                      Re: Problem with upsizing to mysql..."Relation corrupt"

                      Read the details about using Runtime and Shadowed application installs.
                      In RT you can run the app from a single server or pc, but you can also have the data on the server but the app shell downloaded to the connected pc''s.
                      If you let us know what you aim to achieve it might help.
                      See our Hybrid Option here;
                      https://hybridapps.example-software.com/


                      Apologies to anyone I haven't managed to upset yet.
                      You are held in a queue and I will get to you soon.

                      Comment


                        #12
                        Re: Problem with upsizing to mysql..."Relation corrupt"

                        Thanks Ted.

                        So this is an existing 2 PC installation that is currently running, a "POS" PC and backend PC.

                        The PC that I tried to perform the "DB Link" process on gave me the error I posted earlier; however that confused me because the entire Alpha5 application and data is installed on that PC.

                        I'm unfamiliar with the "Shadowed" and "Runtime" installs... you don't happen to have a link do you?

                        Comment


                          #13
                          Re: Problem with upsizing to mysql..."Relation corrupt"

                          It's in the Help section.Once again, please explain what you are aiming to do.
                          Is POS point of sale?
                          Are the two pcs linked in any way?
                          See our Hybrid Option here;
                          https://hybridapps.example-software.com/


                          Apologies to anyone I haven't managed to upset yet.
                          You are held in a queue and I will get to you soon.

                          Comment


                            #14
                            Re: Problem with upsizing to mysql..."Relation corrupt"

                            Originally posted by Ted Giles View Post
                            It's in the Help section.Once again, please explain what you are aiming to do.
                            Is POS point of sale?
                            Are the two pcs linked in any way?
                            Yes, POS = Point of Sale... the PC's are networked.

                            So, I'm finding out the the POS machine stores the actual data and is the Runtime and the other machine is the Developer machine using a shared drive to access the POS machine. That's kind of backwards from how I would have done it but that helped me clear up my confusion, thanks to your information about "Shadowed" and "Runtime".

                            I think I'm back on schedule... thanks for the nudges.

                            Comment


                              #15
                              Re: Problem with upsizing to mysql..."Relation corrupt"

                              ... and another road block just appeared, ugh!

                              So I was successful in linking my table and migrating my data to mysql. However, when opening some of the forms I'm seeing references to missing "Indexes".

                              SNAG-0339.jpg

                              and of course all of the indexes are missing... here is a picture of some of them.

                              SNAG-0341.jpg

                              The documentation doesn't say anything about deleting the indexes???

                              Any ideas on how to get around this problem?

                              Thanks for any ideas or suggestions.

                              Comment

                              Working...
                              X