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 Post Does Not Work

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

    Field Rule Post Does Not Work

    I have a form on built on a table called transaction. I have a field rule that posts from transaction to a table called pickers. When I change a record on the form, the posting rule does not work. If I go to the default browse of transaction and make a change, the field rule post works. Any ideas?

    #2
    Re: Field Rule Post Does Not Work

    it appears to be with a calculated field. What is the timing of a calculated field versus a post to another table?

    Comment


      #3
      Re: Field Rule Post Does Not Work

      On a form, why can you not :
      put a button with action script to set a field value, calculate another field value for the same table, and post the calculated field value to another table using a field posting rule for the first table?

      See sample for details.

      Comment


        #4
        Re: Field Rule Post Does Not Work

        I must not have followed the sequence you meant cause the post field rule seemed to fire just fine when I pushed your button. What am I missing?

        What does step 1 in Scenario 2 mean for us to actually do?

        Comment


          #5
          Re: Field Rule Post Does Not Work

          Nothing more than to observe what the script does. Which is the same thing you would do manually. When I do these same series of events, the calculated value of qoh*price does not get posted to the imu_value table. The qoh and the price fields do, but the value field is blank.

          First table IMU. 4 fields.

          pn user entered
          qoh user entered
          price user entered
          value calculated by qoh*price

          field rules to post/replace qoh, price, value in IMU_VALUE.

          Second table IMU_VALUE

          same 4 fields. all user entered, no field rules.


          If i go into the default browse for imu and make changes using the f3 key, make the changes to qoh and price, press f9 to save it works. All values are calculated and posted correctly. Which is the exact same scenario as 1 on the form, which works.

          But on the form, button1 does 3 things.

          1. it sends f3 to the form to place the form in change.
          2. it sets field values for qoh to 2 and price to 3.33
          3. it sends f9 to the form to save changes.

          All of these steps work correctly. However, while the calculated field in the imu table called value is calculated correctly, it is not posted to the value field in the imu_value table.

          It fails every time. I found this on another database.

          Could this be some sort of a timing issue?

          Comment


            #6
            Re: Field Rule Post Does Not Work

            The button seems to be working fine. Have you forgotten that the button script sets both QOH and PRICE field values before committing the record? Whatever QOH and Price field values are entered by the user get overwritten. The calc field result is 6.66 because the inputs are always 2 * 3.33

            If I'm missing something, furnish a keystroke by keystroke list of steps for us to follow.

            Comment


              #7
              Re: Field Rule Post Does Not Work

              add a button to the form and paste this script in the on_push event.

              sys_send_keys("{F3}")
              topparent:Qoh.activate()
              sys_send_keys("2")
              sys_send_keys("{tab}")
              sys_send_keys("2.55")
              sys_send_keys("{F9}")

              this makes believe the problem has something to do with the set field values command.

              Comment


                #8
                Re: Field Rule Post Does Not Work

                yes that is correct. But, look at the imu_value table after pressing button1. the calculated field "value" does not get posted.

                Comment


                  #9
                  Re: Field Rule Post Does Not Work

                  I would think that pressing button1 this should happen:

                  1. send {F3} to the form to put it in change mode.
                  2. set value of qoh to 2 and price to 3.33, calculate value at 2*3.33=6.66.
                  3. send {F9} to form to save record and post to imu_value.

                  qoh and price get posted. value does not, it remains 0.

                  Comment


                    #10
                    Re: Field Rule Post Does Not Work

                    the above script does the very same thing, except it is key stroke for keystroke what you would do if you were doing it from the keyboard.

                    Comment


                      #11
                      Re: Field Rule Post Does Not Work

                      Alan,

                      I open the form.

                      I push the button to reset (zero out) all the field values in imu_value table.

                      I enter 3 in QOH.

                      I enter 4 in PRICE

                      I push the button to do the post.

                      Field values on screen get changed:
                      QOH becomes 2
                      Price becomes 3.33

                      I examine table imu_value and I see the attached.

                      what am I missing? it seems to be working fine.

                      Comment


                        #12
                        Re: Field Rule Post Does Not Work

                        Set 'Value' property of multiple objects in Form 'imu' .
                        parentform:Price.value = 3.33
                        parentform:Qoh.value = 2

                        'Save record in current form.
                        topparent.commit()

                        This script does NOT work either, the calculated field does NOT post.

                        Comment


                          #13
                          Re: Field Rule Post Does Not Work

                          press button1.

                          Comment


                            #14
                            Re: Field Rule Post Does Not Work

                            1. reset everything to 0 by pressing the button.
                            2. press button1.

                            observe imu_value.

                            qoh=2
                            price=3.33
                            value=0

                            Comment


                              #15
                              Re: Field Rule Post Does Not Work

                              I'll check. (this is why I requested keystroke by keystroke instructions)

                              Later...
                              I see the problem, but have run out of time. Maybe someone else can suggest an explanation.
                              Last edited by Tom Cone Jr; 09-03-2008, 08:07 AM.

                              Comment

                              Working...
                              X