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

Load Primary keys for Parent Table Not Populating Controls

  • Filter
  • Time
  • Show
Clear All
new posts

  • Load Primary keys for Parent Table Not Populating Controls

    Build 6012-5338

    I have a UX with 2 controls. Both controls are bound to a MySQL table. The table has only 2 records.

    I am trying to figure out why the controls are not being populated.

    I added a slider to the Load Primary keys for Parent Table, to show that it is counting the 2 records in the table.

    This is a very small example to demonstrate the issue I am having in a much more complex UX.

    To run this you will have to modify the binding to use your own connection. You can use the table dump file I have enclosed, or create a table with 2 columns.

    Any help is appreciated.

    Here is a video with bad resolution. I think youtube doesn't like my hi-res monitor.

  • #2
    Re: Load Primary keys for Parent Table Not Populating Controls

    I downloaded your UX and followed your instructions. It works for me just fine.

    I made no changes other than changing the connection string and then refreshing the primary key load.

    What version of Alpha are you using? (I am using build 5667)

    If you are using a newer build, I would recommend upgrading all the way to current build and make sure you apply the hotfix.

    If you are using an older build, I recommend 5667. I have been using it for months and it has proven to be solid for me.


    • #3
      Re: Load Primary keys for Parent Table Not Populating Controls

      I am using Build 6012-5338, the latest official release. It has seemed pretty stable so far. I could try rolling back to an earlier release, but since the addition of "Conversion to new format (build 5956) has run" I am leery of doing so.

      Thanks for looking at it.


      • #4
        Re: Load Primary keys for Parent Table Not Populating Controls

        If you are going to go back, back everything up first, then go back. Test this one thing - if it works, submit a bug report - if it still doesn't work, shout back!

        Afterwards, just restore from your backup and move on.

        Note: Alpha didn't change anything in your data. If it did a conversion it was to your UX and grid files. Mostly, Alpha is very backwards compatible. When it converts, it is adding new properties to a UX, but those new properties should not interfere with older versions - they just get ignored.


        • #5
          Re: Load Primary keys for Parent Table Not Populating Controls

          This is what I have found through experimentation. Perhaps you can re-create it...

          Make a simple UX with a few controls, and bind the controls to columns in a single table.

          Add Save_Submitted_Data_to_Table_s in afterDialogValidate event.

          Add a button with {dialog.Object}.submit(); in the onClick event.

          Run it, add some values to the controls and submit.

          Everything works as expected so far.

          Now add another control, and bind it to another column in the same table. Make sure it is Updateable.

          Run it, add some values, and submit.

          The newly added control does not save to the table.

          Remove all binding, and re-create all the binding, and now it saves correctly.


          • #6
            Re: Load Primary keys for Parent Table Not Populating Controls

            I have done that often in my application. It has never failed for me.

            But try this: Repeat those steps.

            Instead of removing all binding, click on the save_submitted action … select Action Scripting at the top and edit action. Just go in and click OK.

            Now try again.

            does it work now?

            I always go into those actions after making table changes.

            If that doesn't fix it, I would submit as a bug. Me testing it wouldn't help because if it worked that way in my version I would know about it by now!


            • #7
              Re: Load Primary keys for Parent Table Not Populating Controls

              Yes I do open the Save Submitted builder every time. Doesn't help.

              This may be a bug. I would like someone to try to re-create it in build 6012-5338, following my steps in post #5.


              • #8
                Re: Load Primary keys for Parent Table Not Populating Controls

                If I update to that build and remember to do it, I will!


                • #9
                  Re: Load Primary keys for Parent Table Not Populating Controls

                  Hi Joe,

                  Just for the fun of it, I created a fresh ux based on the one you supplied.
                  I am using the same build you are, but this works.
                  I have no idea what the difference is, but it clearly works as expected.
                  Attached Files


                  • #10
                    Re: Load Primary keys for Parent Table Not Populating Controls

                    Have you applied the hotfix to build 6012?


                    • #11
                      Re: Load Primary keys for Parent Table Not Populating Controls

                      My first ever youtube video. Someday I might get brave enough to narrate a video.
                      If the video is too grainy, it can be downloaded from here


                      • #12
                        Re: Load Primary keys for Parent Table Not Populating Controls

                        Yes I did install the hotfix for build 6012.

                        Greg, the video is great, but since I have found that deleting and re-creating all the binding settings fixes the problem, then what you are demonstrating in the video will not show the problem, because you are creating the binding from scratch.

                        In fact, using the test UX I attached to my first post will not demonstrate the problem.

                        The extra step that is required is after creating a UX that works as in the video, add another column to the table and add a control to the UX and bind the control.

                        Then see if it works as expected.


                        • #13
                          Re: Load Primary keys for Parent Table Not Populating Controls

                          Hi Joe,
                          I added a column and altered the bindings.

                          alter table carriers add column randomtext varchar(20);
                          update carriers set randomtext = 'Venus';
                          update carriers set randomtext = 'Idaho' where carrier_ID=2;


                          • #14
                            Re: Load Primary keys for Parent Table Not Populating Controls

                            Greg, you are using a different method to add a new column than I use, but t looks to me like you should be seeing the problem occur.


                            • #15
                              Re: Load Primary keys for Parent Table Not Populating Controls

                              What method did you use to add a column ?