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

Double linking field value in child table

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

  • Double linking field value in child table

    I noticed that one child table contains double linking field values. I would really like to know what could cause this behavior because the problem keeps coming back every now and then.

    I attached some screen prints to show the set and field rule settings I'm using. In my case four table's need to share the same adm_nr. Table one (adm) is the parent and the parent key is field “adm_nr” (auto increment is turned on). Table two, three and four are linked as a child to the parent with a “one to one” link type.

    The problem occurred in the second table “adm_bez”. Table two contains the linkfield “bz_adm_nr”. No field rules are specified. However there is a second field in this table with auto increment turned on. I don't believe this could cause the problem but I bring it up just in case.
    Last edited by werder101010; 03-26-2010, 06:48 AM.

  • #2
    Re: Double linking field value in child table

    Werder, the one to one link does not prevent the entry of multiple child table records.

    I see that the "duplicate" records are empty except for the link field itself. Is this typical?

    If this were me I'd study the data entry sequence to determine where my user is permitted to begin a second child table record. And then I'd change the sequence that this can never happen.

    Perhaps they're tabbing through the last field, causing Alpha to save the current record and the automatically begin a new record... and then they shift focus to something else that causes Alpha to save the new "empty" record?

    Comment


    • #3
      Re: Double linking field value in child table

      Thanks for the directions Tom. I will look into the data entry sequence!

      I am afraid I'm a little confused about the purpose of a link field. Should the entry of multiple child table records not be prohibited at all times. If a link in a child table field exists more than once how does Alpha determine which one is the right one?

      Comment


      • #4
        Re: Double linking field value in child table

        From the helps:

        If there are duplicate records, the duplicates are ignored. A one-to-one link forces a parent record to link to a single matching child record, regardless of how many matching child records exist in the child table. The order of the child records, along with the one-to-one link type (first, last, or closest) that you select, determines which child record matches a particular parent record.
        Review the help file topic "One to One Links" for more details.

        Comment


        • #5
          Re: Double linking field value in child table

          I read this before but did not understand it. I now understand it better. Thanks for your input!

          Comment

          Working...
          X