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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Keep Previous Rate / Amounts

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Keep Previous Rate / Amounts

    Every year the county mileage rate changes. How would I write an expression so that when the rate changes, I can keep the previous rate (so the amounts don't change)on all previous records?

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.
    Tags: None
    #2
    RE: Keep Previous Rate / Amounts

    Put the rate field in the record that the calculation is based on. That way you have the elementary components of the calculated field in the same record and when a new rate comes out, only the new records get the new rate.

    Otherwise build a more detailed rate table that has an effective date and a expiration date for the rates. You then have a more complicated calculation and linkage for a set, but you'll save a couple of bytes of disk space.
    You'll also have a history of rates and when they were effective.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment

      #3
      RE: Keep Previous Rate / Amounts

      Hi Ken,

      How about a default table with the rate. Then as the milage gets entered your calculations do a lookup to the default table for the rate. Then the rates stay the same as long as someone doesn't go back and change that record.

      Dan
      Dan

      Dan Blank builds Databases
      Skype: danblank

      Comment

        #4
        RE: Keep Previous Rate / Amounts

        Hi Ken:

        I don�t think you gave us enough information. For example, I�m not quite sure where the county mileage rate comes from. Nonetheless, here are a couple of thoughts off the top of my head.

        For current/previous records, do you have a skip field rule where the express is .T. ?

        As for new records, does the country mileage rate change every calendar year? If so, maybe you can have a lookup table for the rate with two fields, year and rate. That way your lookup table will always preserve the old rates for previous years, while allowing you to enter new records, via the lookup table, at the current rate.

        Robert

        Comment

          #5
          RE: Keep Previous Rate / Amounts

          Robert,

          >>>do you have a skip field rule where the express is .T. ?
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment

            #6
            RE: Keep Previous Rate / Amounts

            Hi Ken:

            [express or expression of .T.]

            Yes that was a typo at 6 am [LOL], obviously I meant expression of .T.

            I was asking if you have a skip field rule on the rate field. If you do and if you use that field in a calculation along with a Skip .T. field rule expression, the rate should always remain a constant.

            Robert

            Comment

              #7
              RE: Keep Previous Rate / Amounts

              Ken,

              I had the same problem in a Q&A application I wrote years ago, but have not had it come up in A5. My problem concerned sales tax. I wanted the sales tax to be computed if my user was in a new record, if not I wanted to sales tax left as previously computed. The pseudocode for the solution went as follows: "if record in add mode, then compute sales tax using appropriate rate in sales tax table, else leave sales tax as is".

              You could write code using this logic and you should have your problem solved.

              Dave
              Dave Jampole
              www.customalpha.com

              Women and cats will do whatever they want. The sooner men and dogs realize that, the happier they will be.

              Comment

                #8
                RE: Keep Previous Rate / Amounts

                Robert,

                No, I don't have .t. as a skip rule. Haven't started to wrote the expression yet.

                Thanks,

                kenn
                TYVM :) kenn

                Knowing what you can achieve will not become reality until you imagine and explore.

                Comment

                  #9
                  RE: Keep Previous Rate / Amounts

                  Dave,

                  Yes, that's the jist of it.

                  Thanks,

                  kenn
                  TYVM :) kenn

                  Knowing what you can achieve will not become reality until you imagine and explore.

                  Comment

                    #10
                    RE: Keep Previous Rate / Amounts

                    I vote for Dan Blank's approach.

                    Make a rate table. Be sure to allow any value so if old records are opened, an update is not forced on them.

                    Or if this only happens once a year,why not just enter a setup field to enter the current mileage and have the rate field lookup on it! It won't keep a history or rates, but you probably don't need it.

                    Yup, I vote for a setup field to change annually - sorry Dan, I take my vote back!

                    Tom

                    Comment

                      #11
                      RE: Keep Previous Rate / Amounts

                      Hey Dave, I noticed you said Q&A, were you a programmer also? I spent many years doing Q&A as a consultant in my area.

                      Comment

                      Previous template Next
                      Working...
                      X