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

Recalculating field posting rules

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

    Recalculating field posting rules

    Hello,

    We are trying to do the following:

    OnRecordChange : re-evaluate the posting rule for field 'a'

    Is there a function or other means of accomplishing this task easily?

    I have done multiple searches throughout the Xbasic Reference and could only find the following.

    .RECALC_CALCFIELDS()

    The field that we wish to have the posting rules re-evaluated is not a calculated field. It is a user typein field.

    Thanks
    Cheryl
    Cheryl
    #1 Designs By Pagecrazy
    http://pagecrazy.com/

    #2
    RE: Recalculating field posting rules

    I found the following as well:

    .UPDATE()

    This looks like it would work but we would need one on the RECORD level vs the TBL level.
    Cheryl
    #1 Designs By Pagecrazy
    http://pagecrazy.com/

    Comment


      #3
      RE: Recalculating field posting rules

      The only thing we have been able to come up with so far is to create calc fields and work with those. Seems like there should be an easier way to work with existing fields so we are still open to any other suggestions.
      Cheryl
      #1 Designs By Pagecrazy
      http://pagecrazy.com/

      Comment


        #4
        RE: Recalculating field posting rules

        Cheryl

        Can you describe what you are trying to accomplish? What I'm seeing is a question about a proposed solution to some other undescribed problem.

        There may be another solution, if we know the problem.
        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


          #5
          RE: Recalculating field posting rules

          Hi Al,

          We have a 'qty' field in our orders table that we have field rules for which will update the committed field in our inventory table. We want the field rules in that 'qty' field to recalculate when the shipping date or status field are changed in the orders table to reverse the prior posting to the committed field in the inventory table.

          I have not been able to find any functions that would allow us to do this with the exception of the recalc on calc fields, but the qty field is a usertyped field. The only option we have been able to think of is to create calculated fields in the order table that will hold all the different products and use those fields to recalculate.

          Hope that makes sense, not real sure how to explain it otherwise. Thanks in advance for any suggestions you may have.

          Cheryl
          Cheryl
          #1 Designs By Pagecrazy
          http://pagecrazy.com/

          Comment


            #6
            RE: Recalculating field posting rules

            Cheryl

            You may want to consider adding records to a transaction table that show the changes and when they occur, rather than having a single record that keeps changing.

            It's always good to have an audit trail, so you can reconstruct the events that lead you to the current time.

            It will also make the posting field rules work.

            Two birds with one stone.....

            Have a great weekend!
            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


              #7
              RE: Recalculating field posting rules

              Hi Al,

              Thanks for all your assistance so far. We are using a memo field to track all transactions that we need an audit trail for which has worked for our needs to date. I looked up the field rule which is on the 'qty' field in the orders table: Date_Ship>{}.and.(status="".or.status="R")

              The problem we are running into is that the data in the qty field does not change, it is when we change the date ship or the status field that we need the posting rule in the qty field to recalculate.

              The current posting rule is working properly and returning the results that we are looking for. What we want to be able to do is the following:

              When I process credit card orders, the shipping date
              gets filled in with the current date, or the status
              field will get a D for declined credit cards and
              cancel this order. When one or both of these fields
              change, we need the qty field to re-calculate and
              reverse the posting that it originally made to the
              committed field ... hence, decreasing the committed
              field in the inventory table as if it never happened
              in the first place.

              Thanks
              Cheryl
              Cheryl
              #1 Designs By Pagecrazy
              http://pagecrazy.com/

              Comment


                #8
                RE: Recalculating field posting rules

                OK, we went ahead and created a calculated field so that we could re-calculate the quantity for inventory purposes when the ship date or status changes in a record. Unfortunately it only reads the fields posting rules when we update a record manually. If we run our credit card update operation it accurately updates the calculated field but does NOT post the changes to the inventory table. Our thought is that it does not read the posting rules in the field during the update query maybe because somewhere this is set to not read them? The update operation runs through thousands of records within seconds so it makes sense that it is 'ignoring all posting rules'. If this is in fact correct, does anybody know how to 'override' this default setting and have it read the posting rules?

                Thanks again in advance for any assistance.
                Cheryl
                Cheryl
                #1 Designs By Pagecrazy
                http://pagecrazy.com/

                Comment


                  #9
                  RE: Recalculating field posting rules

                  Cheryl, some field rules are 'engine level' rules, enforced for the table whether data entry is occuring through a form or not. Others only work when data entry occurs through a form or browse ("UI level"). Which is which has always been a bit nebulous for me. Your description sounds like the post field rule is not an 'engine level' field rule.

                  Consider the following quote discussing the 'honor field rules' flag in the tbl.enter_begin() method:

                  Field_Rules_Flag is an optional parameter. If flag is .T., or is set to HONOR_FIELD_RULES, then "UI level" field rules are enforced when the record is entered (only under special circumstances � see Note below). If the Field_Rules_Flag is .F., then Alpha Five does not enforce these "UI level" field rules. "UI level" field rules are rules such as trigger events, capitalization, minimum and maximum values, masks/templates, lookup fill-ins etc. "Engine level" rules, such as auto-increment values are always enforced.

                  A discussion of which field rules are 'UI level' and which are 'engine level' would be a good topic for the newsletter.

                  An alternative you may wish to try would be to look at the xbasic code beneath your operation to see if the 'honor_field_rules' flag is being set when your table is opened.

                  -- tom

                  Comment


                    #10
                    RE: Recalculating field posting rules

                    Hi Tom,

                    Thanks for the info. There is nothing in the operation code that refers to that flag. Do you think it is possible for me to add it directly into this code and force the field rules to be followed for this one particular field? If so, could you provide me with the syntax that I should use and where I should place it? Your assistance is greatly appreciated.

                    Thanks
                    Cheryl
                    Cheryl
                    #1 Designs By Pagecrazy
                    http://pagecrazy.com/

                    Comment


                      #11
                      RE: Recalculating field posting rules

                      Cheryl, sorry, no. The code you've posted reminds me that the 'update' operation uses a high level utility programmed by the wizards at Alpha Software to do the heavy lifting. We don't have access to its inner workings. Unless someone else has a better idea (and I'll be watching along with you) I fear you're going to have to write a custom version of the update operation from scratch, which includes the posting functionality you need.

                      -- tom

                      Comment


                        #12
                        RE: Recalculating field posting rules

                        So Selwyn, any chance the wizards can give us the inside scoop so that I can get the update to NOT ignore the field rules and post?
                        Cheryl
                        #1 Designs By Pagecrazy
                        http://pagecrazy.com/

                        Comment


                          #13
                          RE: Recalculating field posting rules

                          >>>>yanks all the hair out of my head

                          I have tried an update operation to post to the inv table and have also been playing around with a post operation, not matter what I try I am unable to get the inv data to change :(
                          Cheryl
                          #1 Designs By Pagecrazy
                          http://pagecrazy.com/

                          Comment

                          Working...
                          X