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

Finding a record in a child table

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

    Finding a record in a child table

    I'm new to A5, currently using FM-7. I am trying to query a child field from a parent form. The query returns "no records found" even though the records are indeed there. I know I must be doing something wrong.

    #2
    RE: Finding a record in a child table

    William:
    Check this
    Gabe

    Comment


      #3
      RE: Finding a record in a child table

      flattenquerry()
      Gabe

      Comment


        #4
        RE: Finding a record in a child table

        William,

        Please confirm that your form is based on a set of tables.

        Assuming this is so, there are two different types of queries (at least) that folks might have in mind when they say they want to query a child field on a set based form.

        Sometimes they want to show filtered collections of linked records. i.e. All parent table records remain visible, but only child table records that match the search criteria are shown. In this scenario the filter limits the range of displayed child table records, but does NOT limit the range of displayed parent table records.

        A second and very different kind of query would show only parent table records that have linked child table records that match the query filter. In this scenario the filter on the child table is used to limit the range of displayed parent table records, so that only those parents with linked children that match the filter are shown.

        What are you trying to do?

        -- tom

        Comment


          #5
          RE: Finding a record in a child table

          Hi Tom,

          I am trying to perform the second scenario. The primary table is my "Quote" file and the child table my "Models Quoted" file. I need to do a search on the "Model" field in the child table and return. I am able to do that now, but all the records in the parent table are also returned. I need only the records from the parent table that match up with my search criteria.

          Thanks in advance.

          Comment


            #6
            RE: Finding a record in a child table

            Hi Gabe,

            I am aware of the online manual. I have also printed out the PDF manual... all 855 pages.

            Comment


              #7
              RE: Finding a record in a child table

              Gabe,

              Thanks. I need to find the most straightforward way to handle this.

              Comment


                #8
                RE: Finding a record in a child table

                Two suggestions:

                1) use a cross-level query, run against the set based form; or

                2) design a second set, invert the table relationships so that the child becomes parent, and parent becomes child. Link 1:1.
                Base form on the new set, and query the "new" primary table.

                -- t

                Comment

                Working...
                X