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

Field rules in far away table

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

  • gaby_h
    replied
    Re: Field rules in far away table

    Thanks Tom; I'll give it a try with a Lookup functions.

    Leave a comment:


  • Tom Cone Jr
    replied
    Re: Field rules in far away table

    Gaby, I don't think you can rely on the field rule being "aware of" the existence of linked child tables. I don't think you can simply reference a field in an external table with its name and a "->". The field rule can't see beyond it's own table.

    Having said that it's possible that one of the lookup() functions would suffice, though they can be a bit slow. The condition in your mask would be based on an expression that uses one of the Lookup() functions to retrieve a field value from an external table and then compares it to your string constant.

    Leave a comment:


  • gaby_h
    replied
    Re: Field rules in far away table

    They are all in 1toM link. See attached
    Thanks

    Leave a comment:


  • Stan Mathews
    replied
    Re: Field rules in far away table

    Though you can edit the field rules for the tables in a set as you have done, they are really only table field rules for the chosen table. The set is not "involved" in the field rule.

    I don't think the condition, child1->field = "xyz", in your conditional mask is referring to the record in child1 that you intend. I would guess that it is evaluated against the first record in the child1 table. IOW the field rule does not automatically reference the linked record in child1.

    Without knowing how child1 is linked to child2 is linked to child3 I don't know if you can successfully create an expression like

    child1->field = "xyz" .and. child1->someotherfield = somefieldinchild3

    Leave a comment:


  • gaby_h
    replied
    Re: Field rules in far away table

    Sorry for the lack of info:

    Rule: Mask

    How: I clicked on the set, then Design, then Field rules, then picked the field in Child3, then Data entry tab then used conditional Mask, and in Mask entered 000-0000-000-000 and in Condition entered: child1->field = "xyz" (in the left pane, navigated to the field in child1 and entered the condition)

    Not working: when I enter the data in the field in the emb browse on the form, the mask is not applied, as if there was no field rules.

    Leave a comment:


  • Stan Mathews
    replied
    Re: Field rules in far away table

    The more information you provide, the better answers you get.

    I have created a field rule
    What kind of field rule, how defined?

    It is not working
    Gives an error, yields the wrong result, yields no result, ....?

    Leave a comment:


  • gaby_h
    started a topic Field rules in far away table

    Field rules in far away table

    I have the following structure: Parent ----> Child1 ----> Child2 ----> Child3
    All relationships are 1 to many with ref integrity. I have created a field rule in Child3 that refers to a field in child1. It is not working; I have tried and retried and recreated the set but still not working. Is it because field rules cannot be used in far away tables or because I am doing something wrong?
Working...
X