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

Form Level field rules

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

    Form Level field rules

    Is there a way to apply field rules to a field in an embedded browse?

    #2
    Re: Form Level field rules

    Josh, can you be more specific? Ordinary table level field rules will apply. What is it you are interested in doing?

    Comment


      #3
      Re: Form Level field rules

      I have a typical invoice form based on a set where payments are a child table of the invoice header. I have an embedded browse set up for the payments. I have a button to create a new payment for that invoice and it opens a companion form in Enter mode. I want to default the amount of the payment to the balance due field on the invoice header.

      Comment


        #4
        Re: Form Level field rules

        Josh, you don't need a field rule for this.

        Visit the "Code Archive" forum of this message board. Look for thread(s) discussing how to pass values from one form to another. This will give you some simple xbasic examples.

        Action scripting can do this for you without xbasic coding, as well. In the button that opens the companion form include an action to set the "text" property of the payment amount field in the called form. This is in the action category "Objects Properties (Set and Get)".

        Comment


          #5
          Re: Form Level field rules

          Thanks,
          Will do. Just thought a default in field rules could do it, if it was based on the set.

          Comment


            #6
            Re: Form Level field rules

            Josh,

            There are multiple ways to do anything. Certainly explore the methods Tom has suggested.

            Given the above, I have a question about "balance due". Is it a field in the header table? If so, you might want to think about whether you really want to store it in this way as it is a derived value calculated from debits and credits. (This is the same as the reasoning against storing "age" in a field instead of calculating it from date of birth.)

            If you did the calculation whenever a credit or debit was entered and stored the balance in a variable you could display the variable on any form and use it in an invoice table field rule. To do so, declare the variable in the invoce table's definition screen and make its scope global. Creating the variable in this way makes it available for use in the table's field rules.

            Or, again, you could store the balance in a field and write code to create a default value. Try it both ways to see which works best but there are strong reasons against storing the result of calculations.

            Bill
            Bill Hanigsberg

            Comment


              #7
              Re: Form Level field rules

              I have looked at the alpha sport example and they use the grouping calculations for generating the totals for an invoice. Is that the correct way? I am using posting in field rules instead with stored fields. Is there a pro or con to either method? With stored fields it's easier (I think) to run a report for example, finding invoices with a balance due, if balance due is a stored field rather than a variable. Am I wrong?

              Comment


                #8
                Re: Form Level field rules

                Josh,

                I believe the grouping methods are intended for printing reports (a printed invoice is a report, of course) and may not be reliable in other contexts.

                Your posting rule has a target to which values are posted. This would be a field, correct? If not, where are you storing the value.

                A global variable declared elsewhere is available for use in a report. You need to declare it in the report as well, and with the same scope (global). But you probably would want to calculate each invoice's balance due within the report itself. That way you know the balance will be correct for each invoice. Otherwise you would need to revise the value of the variable for each invoice. Either way, you are recalculating for each invoice. The only difference is where.

                You could easily define a query to capture the subset of accounts for which a balance owing exists. You could also incorporate this calculation into the report's filter expression.

                Bill
                Bill Hanigsberg

                Comment


                  #9
                  Re: Form Level field rules

                  Yes, I am storing the posted values into real fields. Am not using any variables for this purpose.

                  Comment


                    #10
                    Re: Form Level field rules

                    You get the picture. You can continue as you are doing (following Tom's pointers) and get the stored balance into a default expression which you will have to create at the form level rather than in field rules. Or you can step back, reorganize slightly, and do it in field rules.

                    Bill
                    Bill Hanigsberg

                    Comment

                    Working...
                    X