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

Linking Repeating Section on UX

  • Filter
  • Time
  • Show
Clear All
new posts

  • Linking Repeating Section on UX

    I can use some guidance!

    I have a simple UX that creates an order. Of course, there's a repeating section for each item ordered. The UX calculates the Total Amount, Sales Tax, Sub Total, etc. When the user saves the order, it is submitted to a SQL Table. Sounds easy enough, but...

    The way I have it set (which I know is wrong) is that the SQL table has a "JobNum" field that auto-increments when the job is saved (works perfectly). HOWEVER, since the Job # doesn't get its value until the Submit button is clicked, the "detail" fields in the repeating section don't have a Job #... and, therefore, they can't be linked to the main Job table in SQL Server. I hope that makes sense.

    To make it easy to visualize, here's picture of the UX, and the repeating section:

    I don't know if I should, somehow, set the Job # on the client side, before Submitting the Job to the SQL Server... If I do that, I am worried that when multiple jobs are entered at once (during the "busy season", there can be as many as 8 people entering simultaneously).

    Then, I came up with the brainstorm to "Create the Job" when the UX is opened (I used an "INSERT" command in an Ajax Callback. Worked perfectly), which created a unique Job #. BUT, then I didn't know how to capture that NEW Job # to bring it back to JobNum field on the UX. AND, of course, then I have to make sure that Job # is part of every row in the Repeating Section.

    Here are the SQL Commands I used (they work... I just don't know how to get the value from the SELECT command to populate the UX):
    Dim sqlCommand as c
    Dim sqlCommand2 as c
    Dim SetDate as c
    SetDate = Date()
    flag ="::Name::RocBaugh")
    if flag = .t.
    args.set("SetDate", SetDate)
    sqlCommand = "INSERT INTO tblJobInfo (DateOrdered) Values (:SetDate);" 'creates a new record, which issues the next "JobNum"
    sqlCommand2 = "SELECT GetJob FROM qryGetJobNum;" 'get the value just created from a SQL "view" that shows the Maximum value for "JobNum"
    flag = cn.execute(sqlCommand2)
    end if

    I'm sure this is a common scenario. but I'm having a mental block about the right/best way to get this done.

    I'd appreciate any guidance or suggestions you might have.

  • #2
    Re: Linking Repeating Section on UX

    i don't think that's the way to do and to do with ux/dialog is simple. you can study the example they gave like invoice or here is the way to do
    the primary table:
    rest of the fields

    the child table ( for the repeating section)
    job_id (foreign key the one in the parent table)
    rest of the fields

    now create the ux/dialog and bind the fields appropriate table
    then when you submit alpha takes care of submitting the parent first getting the primary id then inserting it into the job_id in the child table for you.

    lot easier than the way you are doing.
    thanks for reading


    version 11 3381 - 4096
    mysql backend
    [email protected]
    Skype:[email protected]
    1 914 924 5171


    • #3
      Re: Linking Repeating Section on UX

      Hi Ghandi-

      Thanks so much for the fast response. I love your answers on the Message Board, because I learn so much from them.

      I assumed I was going about it all wrong and I need some help going in the right direction. I watched Selwyn's "invoice" videos (I don't know if that's what you were referring to). The videos showed how to create the UX (it's pretty much the way I did mine), but the videos didn't talk at all about:
      1) the proper way to "bind" to the tables so that the repeating section and the master sections will both get the "job #"; or
      2) How to get Alpha to "create" a job number that gets sent to the table

      I don't know where to look for that info. Can you point me in the right direction?



      • #4
        Re: Linking Repeating Section on UX

        take a look at this screencast, this is no different from any of the videos that alpha has. just to show you how the binding is done.
        alpha will take care of submitting and getting the primary key to insert in the child table automatically.
        if you have more questions please post back either I or someone else will help you to get going.

        this is how the binding is done:
        Last edited by GGandhi; 04-10-2016, 06:52 AM.
        thanks for reading


        version 11 3381 - 4096
        mysql backend
        [email protected]
        Skype:[email protected]
        1 914 924 5171


        • #5
          Re: Linking Repeating Section on UX


          As always, you are terrific!

          I had several problems: First, I needed to add a separate "ID" field in the "detail" table (and set it to auto increment). Then, I had removed the auto-increment property for the Parent table's Job_ID field (while I was experimenting), so I had to add that to the table as well. Finally, I didn't have the "ID" and Job_ID" fields in the repeating section of my UX (duh?), so I added them.

          It works EXACTLY the way I spent hours trying to get it to work. With your guidance, it took minutes. AND, you're correct. It's very intuitive and makes perfect sense. I'll be able to use that function many times in my applications.

          You are so generous with your time to help people, like me, get up to speed and solve issues. I hope you know how much it's appreciated.

          Have a great day... and thanks again.



          • #6
            Re: Linking Repeating Section on UX

            Thanks Gandhi this really helps a lot