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

Dialog Bind Tables with multiple Primary Keys

  • Filter
  • Time
  • Show
Clear All
new posts

  • Dialog Bind Tables with multiple Primary Keys

    I just spent two hours with Steve Workings on the phone regarding my Dialog parent not working with child table repeating sections. My database is multi tenancy, so I have at least two columns that are primary keys in every table. For instance, in the employee table the primary keys are cid - for company id and empid - for employee id. The child address table then has three primary keys of cid, empid, and addrtypeid. Obviously, the child table links via cid, and empid. The combination of cid and empid in the employee table and combination of cid, empid, and addrtypeid in the address table are always unique. The backend database, PostgreSQL, is working because it will not allow an employee #3 from company #1 to be duplicated with another employee #3.

    The problem is that binding tables does not work correctly with two or more primary keys between the parent and the child tables in the dialog. For instance, when inserting a new employee record, address information from another employee shows up in the repeating sections.

    Steve's solution is to create a column in each table that is autoid and therefore unique. Tables are then linked with these autoid columns. When this is done, the repeating sections work. This seems to me to smack of Y2k type problems that will someday run out of room, not to mention, shouldn't be needed in the first place.

    My question is, why does Alpha 5 specifically say "Primary key field(s)" in the bind to table section. This seems to imply that my way of multiple columns to create a unique primary key should work. But, as Steve points out, mine doesn't work, but his way does. Theoretically, I am right, but practically, I am wrong and Steve is right(as is often the case when I work with him)

    Steve said, "Put it out on the forum and see what other people say." Done

  • #2
    Re: Dialog Bind Tables with multiple Primary Keys


    My question is, why does Alpha 5 specifically say "Primary key field(s)" in the bind to table section.

    I can interpret that phrase in two ways:

    1. Select Primary Key(s) = Please click this button to identify the primary key for each of the tables/views that are used in your component (ie, one primary key for each of one or more tables/views)

    2. Select Primary Key(s) = Please click this button to identify the primary key(s) for each of the tables/views that are used in your component (ie, one or more primary key for each of one or more tables/views)

    Sounds like you interpreted it as #2

    I'm not sure what A5's intention is; from reading Heller's Alpha Five v10 Web Applications: The Tutorial it sounds like they're talking about interpretation #1

    EDIT: after I wrote this, I re-read your post and see that you are referring to dialogs... I have not explored dialogs, but my response is about A5's dialog for beginning a grid. May or may not apply to your question.
    MSQL since 2010
    A5V11 since Feb 2012


    • #3
      Re: Dialog Bind Tables with multiple Primary Keys


      I'm also attempting to use a compound key.
      When I look at the debug information I see the join between my parent table and the table in the repeating section does not have the any join criteria on it
      I thought this may be because I'm using Oracle, but perhaps its more wide spread.
      I have sent support a bug report on this.

      Will keep you posted



      • #4
        Re: Dialog Bind Tables with multiple Primary Keys

        Thanks Garth,

        Thanks Garth,

        I was thinking it was a bug also, but I wanted to be really sure before I posted a bug report.

        I even went so far as to go to Wikipedia to look at the definition of a primary key which is "A primary key is a combination of columns which uniquely specify a row." According to Wikipedia for whatever that is worth.

        So if I am understanding correctly, that is exactly what I am trying to do, uniquely identify a row through the combination of cid and empid columns.



        • #5
          Re: Dialog Bind Tables with multiple Primary Keys


          Alpha have responded... there is to be a fix this the next pre-release build...



          • #6
            Re: Dialog Bind Tables with multiple Primary Keys

            Yes, Alpha has responded. I was gutsy last night and downloaded the pre-release and it did in fact fix my immediate two dialog issues. My issues that were fixed were the multiple column primary key as well as inserting rows into back end SQL child tables from a dialog repeating section, even though the section was not dirty.



            • #7
              Re: Dialog Bind Tables with multiple Primary Keys

              Whoops again.....I was wrong. The pre-release update did not fix the multiple column primary key issues in Dialog repeating sections. I had some left over diagnostic coding in that I had forgot about. The prerelease did fix the insert rows even the the repeating section was not dirty problem.



              • #8
                Re: Dialog Bind Tables with multiple Primary Keys

                Great news to anyone following this thread....Selwyn has fixed the multicolumn primary key problem in dialog repeating sections as of 3/10/2012 update. I am still having a problem with multicolumn primary keys in a row expander sub grid when referencing two tables within 1 grid. I am not sure if this is related, but that was not working yet as of 3/10/2012. I did file a bug report regarding the grid problem.