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

Force Field Rules (OnWroteField) to execute

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

  • Force Field Rules (OnWroteField) to execute

    I have a browse that lists items records. There is a second (lookup) table which contains ranges for various fields of the browse table. Several fields in the browse table use the

  • #2
    Re: Force Field Rules (OnWroteField) to execute

    Hi Janet - Welcome to the board.

    It seems your post got cut off - try again!
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


    • #3
      Re: Force Field Rules (OnWroteField) to execute

      Here's the rest of question...I have a browse that lists items records. There is a second (lookup) table which contains ranges for various fields of the browse table. Several fields in the browse table use the OnWroteField "trigger" in field rules. The OnWroteField script uses the item sku to locate the item in the lookup table, then validate that the the user entered a value that is within acceptable range for that field. I then put the result in a hidden field and use the column properties to modify the font colors in the browse accordingly. My problem is when a user changes the item sku value, the field rules (OnWroteField) for the fields in that row do not execute to refresh their values accordingly. My question: Is there a way to force the OnWroteField trigger to execute for specific fields when the sku changes?

      Comment


      • #4
        Re: Force Field Rules (OnWroteField) to execute

        Are you working with Scan Shark?
        Ted Giles
        Example Consulting - UK
        .

        sigpichttp://ec12.example-software.com//
        See our site for Alpha Support, Conversion and Upgrade.

        Comment


        • #5
          Re: Force Field Rules (OnWroteField) to execute

          No. Not working with Scan Shark.

          Comment


          • #6
            Re: Force Field Rules (OnWroteField) to execute

            Any chance of a small example?
            Ted Giles
            Example Consulting - UK
            .

            sigpichttp://ec12.example-software.com//
            See our site for Alpha Support, Conversion and Upgrade.

            Comment


            • #7
              Re: Force Field Rules (OnWroteField) to execute

              I can provide a sample of the code, but I'm not sure it will add any clarity. The user is testing product samples and entering the test results. Simply put, when the user enters a new record in the browse, I use "Edit Field Rules" to verify, field by field whether each value is within an acceptable range (based on the item#/sku). If, after entering these values, the user goes back and changes the sku , the field rules that validated each field don't re-execute. So, the values are left as they were for the original sku. I'm wondering if I can somehow force the "Field Rules" to execute without the user having to go to each individual field and re-enter a value.

              If you'd still like to see a sample - I'd be glad to provide it. Let me know if you want screen shot of the browse or sample of the field edit code.

              Comment


              • #8
                Re: Force Field Rules (OnWroteField) to execute

                https://documentation.alphasoftware....ld%20Rules.xml

                Try this. You can add that process to a button or automatically OnSave, if I have understood what you are after
                Ted Giles
                Example Consulting - UK
                .

                sigpichttp://ec12.example-software.com//
                See our site for Alpha Support, Conversion and Upgrade.

                Comment


                • #9
                  Re: Force Field Rules (OnWroteField) to execute

                  A screenshot of the browse would be helpful. But you could also embed the browse on a form and pull out the fields for the current record onto the form for editing. Then you can use form or button events to validate & update the data.
                  Robin

                  Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                  Comment


                  • #10
                    Re: Force Field Rules (OnWroteField) to execute

                    Working with a Browse to update records is sometimes a pita.
                    As Robin suggested, a Form Field is easier to handle, but it's your train set and design.
                    If you are amenable I would appreciate a look at where you are at the moment, so a Workspace to see and cogitate over would be great.
                    Ted Giles
                    Example Consulting - UK
                    .

                    sigpichttp://ec12.example-software.com//
                    See our site for Alpha Support, Conversion and Upgrade.

                    Comment


                    • #11
                      Re: Force Field Rules (OnWroteField) to execute

                      I've attached a screen shot of the browse. Here's the code from one of the field rules (OnWroteField tab). I use the "weight_calc" value to set the font color in the browse column properties. It's actually a saved field in the table which is useful when exported to Excel for further analysis.

                      dim sku_current as n
                      dim low_value as n
                      dim high_value as n

                      sku_current=testfile->sku

                      'Get allowable range of values from lookup table
                      low_value=lookupn("F",sku_current,"weight_low","items_qc","Item_Code")
                      high_value=lookupn("F",sku_current,"weight_high","items_qc","Item_Code")

                      if (low_value=0 .AND. high_value=0) then
                      testfile->weight_calc="???"
                      ui_msg_box("WARNING","The Item SKU or Range Values Missing",UI_ATTENTION_SYMBOL)

                      else if (testfile->net_wt < low_value) then
                      testfile->weight_calc="low"
                      ui_msg_box("WARNING","Net Wt is below range. Range = " + low_value + " - " + high_value,UI_ATTENTION_SYMBOL)

                      else if (testfile->net_wt > high_value) then
                      testfile->weight_calc="high"
                      ui_msg_box("WARNING","Net Wt is above range. Range = " + low_value + " - " + high_value,UI_ATTENTION_SYMBOL)
                      else
                      testfile->weight_calc="ok"

                      end if
                      Attached Files

                      Comment


                      • #12
                        Re: Force Field Rules (OnWroteField) to execute

                        I would probably not have created a process this way, but then I don't know all the circumstances.
                        So I created several scenarios using just Field Rules;

                        Between Values
                        From Cross File Validation
                        Greater than or Less than Values
                        Color switching based on values

                        These all act as required with warnings as appropriate from the Browse when data is changed.

                        May I suggest that you add the Re-evaluate Field Rules process to a Button and try that?
                        If you struggle to find this feature, look in the Menu Commands which is in the Code/Action Scripting section.

                        And, I would appreciate a copy of the example app if you have time.
                        Ted Giles
                        Example Consulting - UK
                        .

                        sigpichttp://ec12.example-software.com//
                        See our site for Alpha Support, Conversion and Upgrade.

                        Comment


                        • #13
                          Re: Force Field Rules (OnWroteField) to execute

                          Thank you for your feedback. Sorry, I got busy on another project. I looked at the re-evaluate field rules process, sounds promising. Can I add a button to a browse? Does this go back to the suggestion that a form would be a better choice for this situation? Also, couldn't find the Code/Action Scripting section - is this for forms?

                          Comment


                          • #14
                            Re: Force Field Rules (OnWroteField) to execute

                            Not just for Forms. For everything.

                            Control Panel
                            ..Code Tab - last on the right
                            ....White Space Right Click
                            .......New
                            .........Action Scripting - you have a choice.

                            It would be advisable to create a Form and insert the saved Browse, and then create the Reevaluate Rules.

                            If you wish to use the Native Browse without having it embedded in a Form, add the Action Scripting to the OnRowDblClick in the Browse Properties, to test it.
                            Ted Giles
                            Example Consulting - UK
                            .

                            sigpichttp://ec12.example-software.com//
                            See our site for Alpha Support, Conversion and Upgrade.

                            Comment


                            • #15
                              Re: Force Field Rules (OnWroteField) to execute

                              Originally posted by SCity View Post
                              Can I add a button to a browse?
                              Yes you can add a button to a browse by modifying a column heading and adding a button - along with the normal heading text for that column.

                              AddButton2Browse.jpg
                              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.

                              Comment

                              Working...
                              X