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



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

Re-evaluate field rules for a single open record.

  • Filter
  • Time
  • Show
Clear All
new posts

  • Re-evaluate field rules for a single open record.

    I need to re-evaluate the field rules for the current record only. Can someone help with the syntax?
    I can do it for all records from a button, but I would prefer just the current record.
    Any ideas?
    See our Hybrid Option here;

    If at first you don't succeed; call it Version 1.0

  • #2
    Re: Re-evaluate field rules for a single open record.

    There are no functions to re-evaluate the rules for a single record. If I remember correctly you can use

    tbl ="sometablename")
    'query for the record in question
    'don't change anything

    to cause the field rules to be re-evaluated for the queried record. That may have just been the way to recalc the calculated fields. Memory fails.
    Last edited by Stan Mathews; 11-29-2017, 04:18 PM.
    There can be only one.


    • #3
      Re: Re-evaluate field rules for a single open record.

      You are probably correct Stan.
      When an image is pinned to an ImageReferenceField, there is no factual Record Save.
      I tried simply Saving and that didn't work.
      TableOpen and resave may well solve the issue. Other than that recalc everything is the only option. Still, small ish table.
      See our Hybrid Option here;

      If at first you don't succeed; call it Version 1.0


      • #4
        Re: Re-evaluate field rules for a single open record.

        Since you are probably doing it on a form (?) try making the onchange event for the form field

        There can be only one.


        • #5
          Re: Re-evaluate field rules for a single open record.

          Tried the Stan, but then we hit another problem with the interaction between the sql and dbf tables in the set.
          Ongoing work I'm afraid.
          See our Hybrid Option here;

          If at first you don't succeed; call it Version 1.0


          • #6
            Re: Re-evaluate field rules for a single open record.

            Is there one or a couple of field rule in particular that is of interest? If you are having to push a button anyway, could you have the button run a script that perform the same field rule evaluations on the current record?
            Mike W
            "I rebel in at least small things to express to the world that I have not completely surrendered"


            • #7
              Re: Re-evaluate field rules for a single open record.

              There are 6 fields Mike, each of which has a field rule attached.
              A script to do that would be good.
              See post#3. There is a Save when an image is selected and I need to get the file path and save it. A Calc expression does it fine and my work around to force a recalc is to clear a logical field which must be ticked to confirm acceptance. This has the effect of a record change, so the rules are recalculated.
              See our Hybrid Option here;

              If at first you don't succeed; call it Version 1.0