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

Linking Field in Child Table Doesn't Show

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

    Linking Field in Child Table Doesn't Show

    I have a set with 3 1-m child tables. All are linked by case number to the parent table. Two 1-m child tables show the case # in the case # field OK. The third one doesn't show the case # in the case # field.

    Any ideas what's causing this?

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Linking Field in Child Table Doesn't Show

    Ken, the values in the linking field in each child table should "show" just fine if you look at the tables using the default browse or form for the table alone.

    Likewise, if you build a form based on any of the child tables, the linking field and its values can be dropped in place and will be visible.

    I suspect that you are trying to see these values using a form based on the set, not on the child table. In this case, I believe Alpha Five automatically suppresses the display of the linking field. Probably because this field gets filled in by Alpha Five when a new child record is added through the same form.

    If you need to base the form on the set, *and* you need the user to see the value of the linking field in each child table, you could display them in variables on each child table form. However, be certain that you control the edits so that the user doesn't have a chance to break the link between the child table and the parent.

    -- tom

    Comment


      #3
      RE: Linking Field in Child Table Doesn't Show

      Tom,

      Thanks for the clarification. This is exactly what happened, the form is based on the set. I don't need to see or include the field, I just happend to do it that way.

      I think this is one of those subjects that have surfaced lately. I hope, when V5 comes out, the new manual will cover the advantages and disadvantages of creating forms, browses, etc via a set or table, embedded, not embedded, etc. The manual doesn't cover thses subjects and those of us who are switching from A97 or other Db's, really struggle with this. I don't understand why A5 has to have numerous ways of creating forms and browses. Although we have Db experience, we have to relearn and reprogram our thinking. Kind o like remodeling a house vs building a new one, You have to tear apart before you can build.

      Thanks again for the clarification.

      ken
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #4
        RE: Linking Field in Child Table Doesn't Show

        Ken, an easy example of what I was trying to describe is available in the Invoices database (sample) which shipped with Alpha Five.

        Open the default browse for the Vendors Set.

        This is set contains two tables: the parent table is Vendor, and the child, linked 1 to many is Product. The child linking field is "Vendor".

        When you examine the browse for the child table you will see that there is no column for the child linking field, Vendor. If it were displayed, every value would be the same, so it's likely the designers of Alpha Five thought that it would be redundant to display them one after the other. Also, if these values in each child record were displayed in a "live" browse object, the user might be tempted to modify values in this column of the browse. This would of course destroy the "link" in each case.

        With this additional explanation maybe the absence of the child linking field makes more sense?

        -- tom

        Comment

        Working...
        X