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



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"

  • Filter
  • Time
  • Show
Clear All
new posts

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

    Anyone have any thoughts or ideas on how to address forms that have buttons tied to indexes (filters) that no longer work after linking tables to MySQL?

    Is it possible to attach straight SQL to them eliminating the indexes?



    • #17
      Originally posted by ampapa View Post
      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".


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


      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.
      I'm resurrecting this project again to try and help get my friend over the hump with his upsizing project and I was unable to get any resolution to the index problem that appeared after migration. I don't see any direction in the documentation nor can I find any suggestions or hints on the website or via Google search, definitely stuck here!

      Can anyone assist with a solution on how to migrate or recreate the missing indexes? From what I can find he has a handful that I will need to be address.

      I'm guessing these need to be recreated in SQL, but where and how do I link them back to the forms using them??

      Further researching and digging hasn't found a solution to this problem so any help or suggestions would be much appreciated.




      • #18
        Moving DBF to SQL is only data.
        It doesn't recreate forms or indices, that's up to you.
        SQL indices are a little special, so beware.
        Research Where Clause and Order By.

        Suggest you start with a simple form attached to one table, then try filters and selection based on Where etc.
        Last edited by Ted Giles; 07-18-2020, 01:24 PM.
        See our Hybrid Option here;

        There are 3 things you can do in any situation;
        Live with it, Change it or Walk away from it.


        • #19
          Many thanks for the reply Ted.

          With my unfamiliarity with the application, is this a form related problem? These don't appear to be actual indexes on the tables...

          How do I know what forms are utilizing the "indexes"? ID there somewhere I can see a list of them?

          Just trying to figure out what it is I'm trying to solve for here..



          • #20
            There are no Indexing options shown against an SQL table in the Alpha IDE.

            Double click on a SQL table in the Alpha IDE
            View the records
            Try creating a Query - Server Side
            Try the same with Client Side
            Note the difference.

            Server side is quick, Client side requires all of the data to be downloaded so can be slow.
            There is an AUTOMATIC function which decides whether to use Client or Server side based on volume of records - when you create a Query you will see the option of an explanation.
            Read this as it describes the Automatic process and you will be familiar with the Query construction which you can then use and it will be held locally and available to use with a Button.

            Suggest you convert all of the Indices to Queries and attach them to Buttons.

            As for finding which indices are in use, if you don't have A5DOC, then you may need to look at the buttons you mention and change them one at a time.

            See our Hybrid Option here;

            There are 3 things you can do in any situation;
            Live with it, Change it or Walk away from it.


            • #21
              Again, I appreciate the insight.

              So, are the Alpha "Indexes" more like macro's associated to buttons that in turn return a resultset in a form/report?


              • #22
                Yes, essentially.
                See our Hybrid Option here;

                There are 3 things you can do in any situation;
                Live with it, Change it or Walk away from it.