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

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

Bug in parent-child-grandchild 1:M:1 set?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Bug in parent-child-grandchild 1:M:1 set?

    The attached is an example with a three table set with Parent:Child 1:M and Child:Grandchild 1:1. I believe this would fall into Dr. Wayne's example of three table set with parent = patient_header, child = patient_visits, and grandchild = visit_notes scenerio.

    The attached shows this does not work.
    1. All grandchild record for a parent are shown, not the grandchild specific to the child.
    2. You are unable to add a grandchild for a new child
    3. When you try and delete the grandchild, it deletes the child.
    4. It is displaying 4 grandchild records for parent record #3, one as showing twice when there are only 3 grandchild records in the table and there is not a duplicate.

    Please confirm before I send in as a bug. Thanks.
    build: 1815:3211
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: Bug in parent-child-grandchild 1:M:1 set?

    Mike, I think what's wrong is the use of an embedded browse for the 1:1 grandchild table. Compare your form to the default form for the set, to see what I mean. I don't think it's correct to use an embedded browse object for a child or grandchild that's linked 1:1. -- tom

    Comment


      #3
      Re: Bug in parent-child-grandchild 1:M:1 set?

      As Tom suggests, the "correct" way to display a 1:1 grandchild is within the child browse.
      Peter
      AlphaBase Solutions, LLC

      [email protected]
      https://www.alphabasesolutions.com


      Comment


        #4
        Re: Bug in parent-child-grandchild 1:M:1 set?

        ... or by dropping fields from the grandchild table directly on to the form, as per the attached example.

        Comment


          #5
          Re: Bug in parent-child-grandchild 1:M:1 set?

          See the attached modification of Mike's db which successfully shows the grandchild and correctly marks the grandchild.
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: Bug in parent-child-grandchild 1:M:1 set?

            The display per se shouldn't make any difference, what matters is whether the ref integrity is turned on or not. See related thread.
            Didn't open Mike's zip, but would be quite hesitant to call it a bug.

            Comment


              #7
              Re: Bug in parent-child-grandchild 1:M:1 set?

              Tom,

              I get an error message using either of your delete GC buttons.
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                Re: Bug in parent-child-grandchild 1:M:1 set?

                They're not my buttons. Did not do anything other than delete the browse object and replace with fields from the grandchild table.

                Comment


                  #9
                  Re: Bug in parent-child-grandchild 1:M:1 set?

                  Originally posted by Tom Cone Jr View Post
                  They're not my buttons.
                  Shows you how how observant I am.
                  Peter
                  AlphaBase Solutions, LLC

                  [email protected]
                  https://www.alphabasesolutions.com


                  Comment


                    #10
                    Re: Bug in parent-child-grandchild 1:M:1 set?

                    Mike's data reveals an issue I haven't bumped into before.

                    Use the default form for his set.

                    If a child record has no linked grandchild record, the browse displays field values from the last physical grandchild record anyway.

                    I see the same thing in my example, where I deleted the embedded browse object and dropped grandchild fields directly on the form.

                    This seems wrong to me. What am I missing?

                    Comment


                      #11
                      Re: Bug in parent-child-grandchild 1:M:1 set?

                      Originally posted by Tom Cone Jr View Post
                      This seems wrong to me. What am I missing?
                      The GC is linked by "closest". Change it to "first" and you won't see a GC where there isn't one.
                      Peter
                      AlphaBase Solutions, LLC

                      [email protected]
                      https://www.alphabasesolutions.com


                      Comment


                        #12
                        Re: Bug in parent-child-grandchild 1:M:1 set?

                        Thanks, Peter. Should have seen that myself. Guess I'm so used to using link "first" that I didn't check it. -- tom

                        Comment


                          #13
                          Re: Bug in parent-child-grandchild 1:M:1 set?

                          I guess to conclude this thread, this example sums up what has been said. Thanks.
                          Mike W
                          __________________________
                          "I rebel in at least small things to express to the world that I have not completely surrendered"

                          Comment

                          Working...
                          X