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

re-evaluate rule

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

    re-evaluate rule

    I've seen a few discussions on this topic, but none had the
    answer I am looking for. I know how to get to the control
    panel to do this, but is there a way or a scipt you could
    write to do this for you. I have a calculate field that
    does what its suppose to do and the results is posted to
    another table. Example, I have a payment field that post based on a date. If the last payment is to be on 7/26/04 I
    don't won't anymore payments to show up after that date,
    however on 7/27/04 this posted payment does not go away
    until I go into the control panel and click on the re-evalute rule, then it updates to zero. My calulated field
    is: If(System-"date"ExpDate,0,price/months) If system date
    is greater than the expiration date (last payment) then
    the payment is 0, else purchase price/number of months to
    give the monthly payments. You solve this one and I promise I won't ask anymore dumb questions (Ha)
    btw, this is a depreciation file that we have to spread out
    over 5 years or 60 months and the monthly payments are considered a monthly expense until the time runs out, but
    after that it continues on and I need to stop it.

    Maybe someone already has such a file

    Jerry

    #2
    RE: re-evaluate rule

    The simplist way to force a recalcualte, other than from the field rules, is to open the record, place it in change mode and save it. That will force all calculated fields to evaluate. You could create a query to find all records where that last date was before the current date and then create a fetch loop to open each record, and resave.

    For example, if your table is named "mytable", you could do the following

    query.filter = "ExpDate " date()"
    query.order = "" ' the order doesn't matter
    tbl = table.open("mytable")
    idx = tbl.query_create()

    if idx.records_get() " 0 ' some records found
    tbl.fetch_first()
    while .not. tbl.fetch_eof()
    tbl.change_begin()
    tbl.change_end()
    tbl.fetch_next()
    end while
    end if
    tbl.close()

    This should be fairly fast, depending on the size of the table.

    Jerry

    Comment


      #3
      RE: re-evaluate rule

      Jerry

      Thanks for this, it works on the depreciation file, but
      does not update the amount that is posted to the other
      file. What I really need is the amount that has been
      posted to another file to go away after the expiration date. I'll work some more on this and if Tom or Stan
      can come up with something on this it will be appreciated.

      Jerry

      Comment


        #4
        RE: re-evaluate rule

        Jerry,

        I believe what you're seeing is working as designed. Most of the table field rules were designed to run when data entry occurs through a form or browse, not when the table is being manipulated behind the scenes with a script. The post field rule falls in this category I believe. Your script will probably need to be modified to change the field value in the other table to zero when the calc field evaluates to zero. In orher words the script is going to have to do the work, the post field rule won't.

        -- tom

        Comment


          #5
          RE: re-evaluate rule

          Ok, forget the posting rule thru field rules. I was able
          to do it via the post operation:

          a_tbl = table.current()
          post.t_db = "c:\ftrakw\depsch.DBF"
          post.m_key = "VEHID"
          post.t_key = "VEHID"
          post.m_filter = ""
          post.t_filter = "expdate"date()"
          post.m_count = 1
          post.m_field1 = "Other"
          post.m_exp1 = "Other+@Depsch-"Payment"
          post.t_count = 0
          a_tbl.post()

          BUT --- when I run it more than once it will post the paymemt field to the other field and will add the payment
          each time I run it causing the other field to increase.
          I now need to set the other filed to zero prior to running
          this.

          Again as usual
          Thanks

          Jerry

          Comment

          Working...
          X