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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

    Hi
    In my UX i have a main table - Quotations (primary key QuotationID) . I have a list of products in that quotation which are presented in a List control bound to a QuotationLines table (primary key QuotationLineID). Editing in the list control is done through the Detail View.
    I then have 4 or 5 repeating sections, which are grand children, i.e connected to QuotationLines through QuotationLineID in a one to many relationship

    The Tables binding dialog in the UX does not let me do the above setup. It needs the QuotationLines table as top level in order to let me enter the RS corresponding tables.

    How can i achieve the above?

    Thanks
    Jaime
    Tags: None
    #2
    Re: Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

    Alternatively, is it possible, in a UX, to have a List Control for a parent table, then in the detail view of that list have a List Control for the children, which has in it's detail view Repeating Sections for the grand children?

    Comment

      #3
      Re: Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

      You won't be able to use repeating sections this way in a single UX. You could cascade lists. So the best you can do in this scenario is have the grandchildren also be lists with detail views.

      If you need the grandchildren to be editable repeating sections, then create a new UX with the quotation line as the main record. When you need to edit the grandchildren, open this new UX - with the quotation lines as the master form, you should be able to create repeating sections for all the other tables.

      Comment

        #4
        Re: Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

        I see what you mean. This would work but won't cut it with the customer.
        What i am trying to achieve now is as follows:
        Quotations List with detail view for a few fields ( customer, date and totals )
        QuotationLines table set as master table and as child list as well
        Repeating sections as children of quotationlines table.

        Would that work?

        Comment

          #5
          Re: Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

          I don't think that will work either.

          Instead, you may simply have to use the UX to hold everything and do all of the data manipulation yourself.

          In other words, instead of using the UX to control the data saving, you write it yourself.

          This is a more difficult way to go about it, but it can be done.

          Alternatively, if you don't need to worry about using this app on smaller screens, you could use grids instead of repeating sections. You could link the grids in and keep the UX to just the Quotation and the QuoteLines.

          Comment

            #6
            Re: Parent with Children ( List control ) and grand children ( repeating sections ) binding nightmare

            Panel cards are awesome in large UX components like this (or with some complexity) because you can simply create another list with a detail view to edit the "repeating section" They can be child lists that are filtered by the parent list and refresh when you open them. To me that would be the easiest way to accomplish your goals - that is of course if I am understanding them.
            I prefer to put all of my navigation in the panel headers and then the save/delete in the panel footers since that allows for the lists to fill the panel cards and scrolling works like a charm then. Good luck!
            NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

            Comment

            Previous template Next
            Working...
            X