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 error

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

    Linking error

    This is the error message "For integrity Use Parent Field Name".
    This is the situation. I have jobhdr=>jobdet=>inventsel.
    I need referential integrity on.
    The first link is jobhdr->jobid linked to jobdet->jobid+planid.
    The next link is jobdet->jobid+planid linked to inventsel->jobid+planid+place.
    When I use that last link I get the error message and can't go further.

    In plain English I need to have the jobid and planid automatically entered into the inventsel record.

    What does the error message want to tell me??

    TIA,
    Dorothy

    #2
    RE: Linking error

    Can you use multi-field links with referential integrity? I vaguely recall that this is a no-no. Am I getting this mixed up?


    -- tom

    Comment


      #3
      RE: Linking error

      I've had problems in the past trying to use more than one field in the parent link. I don't know if that's the cause of your error, but you might try creating a new field in the second table that is a calc field, concatening the two fields you want, and then use that calc field in the link.

      Comment


        #4
        RE: Linking error

        Dorothy
        The following should cure the problem
        Parent file: define concatinated field for link
        Child File : Same
        Set Link "Concatinated field", referential integrity on.
        As A5 does not allow referential integrity on multi field keys, you must fake it out and use a concatinated key. This is a messy workaround (not proper data base design), A4 handled it well. Hopefully a future release will return A4's functionality ??
        I have found this necessary in many applications.
        John Gamble

        Comment


          #5
          RE: Linking error

          Hi all,

          I don't disagree with the previous suggestions but it is (at least supposed) to be possible to combine referential integrity with a compound linking key.

          Take a look at the new features list for version 4.01. It is on pg. 12 of the pdf version of the 4.03 readme. The gist of it is that the linking expression must refer to the fields in the same order as they appear in the table definition.

          Since the ordinal position is of no other importance this is an easy condition to meet. Simply edit the table structure.

          Notwithstanding the above, I would rigorously review my reasons for opting for referential integrity. I have concluded that I have tended to overuse this feature which does impose a cost. Of course when you need it, you need it.

          Bill
          Bill Hanigsberg

          Comment


            #6
            RE: Linking error

            I have a set that uses 1:1 and 1:many links. All forms etc work fine. When changing a single character field from 20 to 21 characters in width, I get the following message in either opening or designing a layout based on the set.

            "for integrity, use parent field name"

            I went into the set to define the links with the table name prefixes and it still fails, however, setting back the width makes everything work OK again. I suspect their is an implicit width stored in the set definition and/or layouts, but have no proof of this.

            I may have to change the table and then do a file copy which may fool A5. Or maybe not?

            Regards,

            Ira J. Perlow
            Computer Systems Design & Associates
            [email protected]
            Regards,

            Ira J. Perlow
            Computer Systems Design


            CSDA A5 Products
            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
            CSDA Barcode Functions

            CSDA Code Utility
            CSDA Screen Capture


            Comment


              #7
              RE: Linking error

              And the answer is that despite the message, what it was really saying was that the parent key and child key of the multi-field keys (Which were sequential in the structure of both - if that matters) were not the same key lengths. Changing the child and parent structures to the same width of the changing field eliminated the problem

              Regards,

              Ira J. Perlow
              Computer Systems Design & Associates
              [email protected]
              Regards,

              Ira J. Perlow
              Computer Systems Design


              CSDA A5 Products
              New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
              CSDA Barcode Functions

              CSDA Code Utility
              CSDA Screen Capture


              Comment

              Working...
              X