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 rule posting

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

    field rule posting

    Hi,

    I thought I set up a field rule to post data from another table, but it's not working. I designed the rule in Table1, and want data to come from Table2. Is it supposed to be the other way around, wherein I need to write the rule in Table 2 - the table where the data comes from?

    If this is the case, it won't work for me. Help, as usual, is very little help. I also don't see any reference to field rule posting in the A5v3 manual.

    Any help would be appreciated.
    Thanks,
    Wanda

    #2
    RE: field rule posting

    Wanda, the terminology can be a bit confusing.

    Generally, if you are working with table1 and need to retrieve values from table2 and insert them in table1 this is a 'lookup'. You have no value, so you 'look it up' in the external table.

    On the other hand, if you have a value in table1 that you want to send to table2, this is called a 'post'. You have a value, so you 'post' it to the external table.

    Hope this helps keep them straight.

    You'll find the descriptions of lookup and post field rules in the user's guide.

    -- tom

    Comment


      #3
      RE: field rule posting

      No, it doesn't help at all, but thanks for the info...you're always so eager to help and I appreciate it, immensly.

      I'm actually trying to avoid using a look-up, but am reserving it for my second choice.

      I've looked in Help and in the manuals I have, but can't find anything to help me with a post operation as a field rule.

      I use posts operations quite frequently, as an Operation - but haven't tried up to now to use it in the field rules.

      Any experience with that, yourself?
      Thanks,
      Wanda

      Comment


        #4
        RE: field rule posting

        Just thought I'd add that this particular table is the one I've had all sorts of problems with - making me thing again (and again, and again!) that it's corrupted. 1) It can't "find" data that I know is there because I can see it. 2) Every time I cut or delete a record, the table crashes (performs an illegal operation), and now the field rules don't seem to be working right.

        I can't bear the thought of recreating the whole thing. I've already copied, renamed, etc...but to no avail. I'm trying to just hang in there until the bugs get worked out of v5 (thank you to you gals/guys finding and reporting them!!!)

        So, if you can't see that I am trying to post to/from in a backwards fashion (ie. Table1 should have the field rule instead of Table2), then just forget it for now.

        Please let me know.
        Thanks,
        Wanda

        Comment


          #5
          RE: field rule posting

          Your initial description makes me think you are in fact doing it backwards, as I tried to explain.

          Check the User's Guide, beginning at about pg 81, for a lengthy discussion of when and how to implement a posting rule. Your initial description suggests you might want to put the posting rule in table2, and use it to update values in table1.

          Comment


            #6
            RE: field rule posting

            Wanda, if you are using Alpha Five, vers 3, I would definitely recommend you upgrade to vers. 4.

            Comment


              #7
              RE: field rule posting

              Wanda:

              Have you tried lookup[letter, i.e. 'c', 'n', etc]. This is a way to retrieve information from another table for input in the current one.

              Using a lookup function you can set the field to default at the value of the looked-up table's field value.

              Something you might consider.

              Ken

              Comment

              Working...
              X