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 Rules Posting

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

    Field Rules Posting

    I have a payments table with an amount field that through field rules updates a deposit field in the OrderHeader table.

    On an Order entry screen where the payment table is in an embedded browse the posting rule works properly, but if I create a button to open up a companion form to enter a payment the posting rule does not work.

    #2
    Re: Field Rules Posting

    If you post a zipped copy of the application maybe we can spot what's gone wrong, or at least corroborate the behavior. If the companion form is based on the payments table I would expect the payment table field rule to work just fine.

    Comment


      #3
      Re: Field Rules Posting

      Thanks Tom.
      I got it working.

      Comment


        #4
        Re: Field Rules Posting

        I got it working.
        Barry,

        How wonderful for you!


        If you were to describe how you "got it working", the next person who encounters a similar problem and, God forbid searches for a solution, might find your posted answer and not have to ask the same question.
        There can be only one.

        Comment


          #5
          Re: Field Rules Posting

          Hi Stan,
          To be honest with you Im not sure what fixed it. I developed this form over a year ago and have not done any work in Alpha since then. Trying to get started in Alpha again.

          I did find a base filter on the form that did not make any sense and I removed it. I was also originally calling the form from another form and limiting the view to one record. Now I am executing it straight from the control panel and it is working.

          Comment


            #6
            Re: Field Rules Posting

            Well I thought I had it working.
            Please open the Order Entry form, Create a new record and use the payment button to add a payment.

            I have tried a variety of refresh object & display commands, but can't seem to get it to work reliably.

            Comment


              #7
              Re: Field Rules Posting

              Barry, I don't think it's a refresh issue. The field rule is not "adding" the amount to the Total_deposits field of the OrderHeader table in the first place, although I only see this happening with the first Payment on an Order. Once a payment record has been entered, subsequent payment records seem to be posting just fine. Very strange. It's too early to call this a bug, let's wait for others to corroborate, but it is beginning to look that way.

              -- tom

              Comment


                #8
                Re: Field Rules Posting

                Barry and Tom

                I downloaded the zip file and opened the file in V10.

                Followed Barry's directions.

                Opened the order entry form. Entered a new record. Entered some items. Then clicked the payments tab. The clicked on the Add Payment button. The payments form came up and I added a check payment for the full amount of the order. Then clicked on the save button which returned me to the main form. Also tried it with a partial payment. This is how I perceived your directions.

                The payment immediately showed in the payments browse and was posted to the order header.

                That was runnig V10 Version 2736-3523 worked as it should


                Then tried 2814-3539 got the same results as Tom when the first payment is entered it does not post. Payment after that, it posts.

                So I would say that between 2736-3523 and 2814-2539 something was broken.

                Barry what version are you running?


                Tom Baker

                Comment


                  #9
                  Re: Field Rules Posting

                  Same build as tom's The latest.

                  Comment


                    #10
                    Re: Field Rules Posting

                    Got the following response from Selwyn.

                    "i don't think that this is a bug.

                    you can't post to a record that is in either enter or change mode.
                    you need to save the record before you can post to it."

                    Is this really the case?

                    Comment


                      #11
                      Re: Field Rules Posting

                      What Selwyn says is true. However, in my testing here, I saved the new InvoiceHeader record before adding the payment record.

                      Comment


                        #12
                        Re: Field Rules Posting

                        Entered a new record into the orderheader and then saved the header record.

                        Went into the orderlines browse for that header record and entered an order.

                        Saved that.

                        Then went to control panel and opened both the orderheader and orderlines default browses and they both show that the record had been saved.

                        Went back to the form and that same order id and clicked on button Add Payment. Then added a partial payment for that transaction and saved the record. The payment browse was updated with the correct amounts however there was no posting to the order header total deposit field nor recoed.

                        Evidently Selwyn did not check it out, just relied on what should have been.

                        As Tom already stated he did basically the same thing as the above and it still did not work.

                        Needs to addressed again with Selwyn to have him at least test the sample that you sent him.

                        That just my two cents worth.

                        Tom Baker

                        Comment


                          #13
                          Re: Field Rules Posting

                          I checked it again and your right. BTW it also works properly in the last build of V9 even when the order header has not been saved.

                          Comment


                            #14
                            Re: Field Rules Posting

                            Originally posted by barry685 View Post
                            I checked it again and your right. BTW it also works properly in the last build of V9 even when the order header has not been saved.
                            No, the header record has to be saved.

                            This may be saved by moving within the form and invoking an automatic save. But a post will not add a record to the table it is posting to...
                            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


                              #15
                              Re: Field Rules Posting

                              Al,
                              Is there any indication on screen of what mode a record is in?

                              Comment

                              Working...
                              X