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 enforcement

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

    Field rule enforcement

    Hello All ,

    When you are editing a table in Xbasic by �Tbl.change_begin(.t.)� ,
    what field rules are enforced .For example are posting rules enforced ,are events like CanSaveReord enforced. I have not been able to find any information from help documents. All I could find out is that the �UI level� rules are enforced, but what rules
    are �UI level� . I appreciate any help .
    Thanks
    Nick.

    #2
    Re: Field rule enforcement

    UI stands for user interaction. UI level rules are those that have to do with manual data entry. IOW, how could Alpha enforce a lookup requiring a user choice, during xbasic record entry?

    See this.
    There can be only one.

    Comment


      #3
      Re: Field rule enforcement

      That being true, however Nick
      If you were to try, use Xbasic as you describe, change a field that has a field rule value calculation.
      You will see that you incur an error and get a warning message. As I say try it - best way to discover things.

      Comment


        #4
        Re: Field rule enforcement

        Thanks Stan
        In the wiki page (the link you sent) say that tbl.enter_begin(.t.) enforces posting
        Rules .Does that also work with tbl.change_begin(.t.)?
        In the wiki page for tbl.Change_begin() it says that with the (.t.) option UI level
        Rules are enforced .posting and events are UI level are they not?
        In my code tbl.enter_begin(.t.) enforces these rules but tbl.change_begin(.t.)
        Does not .is there a differencre ?

        Comment


          #5
          Re: Field rule enforcement

          Nick, the first paragraph in the link that Stan sent you explains exactly which field rules.
          In the next it says is IN ADDITION to which, same field rules are observed and those not now using the .enter_record(), .change_record() and .delete_record() Methods.
          The difference between tbl.enter_begin(.t.) enforcing rules but not tbl.change_begin(.t.) is that some field rules, like auto increment, are activated only upon creating a new record.
          The question to ask is why do you want anyway to change fields that are controlled by field rules anyway?
          Maybe they should not be set at field rule level for your purposes.

          Comment


            #6
            Re: Field rule enforcement

            Thanks Ray,
            If you look at the bottom of Stans link .It says:"
            Posting Rules Now Honored During Xbasic Data Entry

            The following Interactive Window session (for AlphaSports) shows that Posting Field rules are now honored when data entry is performed using Xbasic. Previously, they were only honored when doing edits using the user interface."

            above was the exact quote from the page.
            The reason I like to use the rules is that I like to use the posting feature.I could not find any refrences to change_record() in help file ,it is also not listed
            in the table method&function list ,have you ever used it in this context.

            Comment


              #7
              Re: Field rule enforcement

              I use ..enter_record() almost exclusively as opposed to enter.begin(). Mostly when writing on or copying most or all fields and just changing a few
              If I already have the dot variable populated I often use change.record()..
              Posting rules I don't use, mainly for the type of apps I do that involve at least a couple of contra-entries and additional postings. Easier to keep track of what is happening in one place.

              Comment


                #8
                Re: Field rule enforcement

                Originally posted by Farzadalpa View Post
                Thanks Ray,

                The reason I like to use the rules is that I like to use the posting feature.I could not find any refrences to change_record() in help file ,it is also not listed
                in the table method&function list ,have you ever used it in this context.
                Same here

                Comment


                  #9
                  Re: Field rule enforcement

                  Reason is that it is NOT in the help file, it should be.
                  So now you get introduced like I was on October 2011 (thanks Robin) in another post

                  It allows in three steps 1.copy a record to pvar, (2. change any fields) 3. append a fully qualified record
                  User wont necessarily see errors when a field rule prevents change, unless you set an error pointer to view the details. But you expect it not change those anyway.

                  Comment


                    #10
                    Re: Field rule enforcement

                    I tryed change_record() and it did not enforce neither Cansavercord or the posting.
                    So it seams that these rules can not be enforced by Xbasic despite the documentations .I wonder if its a bug.
                    I may send a bug report .

                    Comment


                      #11
                      Re: Field rule enforcement

                      Nick
                      Please clarify by way of example.

                      If I use field rules, its intended only for user entry where it is visible. When I use xbasic to work with records I manage that myself and honour the rules.
                      I actually don't know - Should a posting field rule should trigger repeatedly every xbasic change? At that point you are in control not the user (UI)
                      I don't think Honour is the same as Trigger.

                      I follow this method, its the quickest way to get the job done
                      I learn how it does work then I program it the way I want it to work if different.

                      Comment


                        #12
                        Re: Field rule enforcement

                        Ray
                        Your are right about having to code the postings myself .
                        I took me half hour to code it and I waisted two day fiddling
                        with the field rules.
                        But in answer to your point about the triggering Ui rules , the
                        .t. or .f. options in change_begin() is supposed to control that
                        .
                        Thanks for all the help.
                        nick

                        Comment


                          #13
                          Re: Field rule enforcement

                          Well done.

                          Comment


                            #14
                            Re: Field rule enforcement

                            Originally posted by Farzadalpa View Post
                            Ray
                            Your are right about having to code the postings myself .
                            I took me half hour to code it and I waisted two day fiddling
                            with the field rules.
                            But in answer to your point about the triggering Ui rules , the
                            .t. or .f. options in change_begin() is supposed to control that
                            .
                            Thanks for all the help.
                            nick
                            Nick, may you pls share a sample on how to code field rules?Thanks!

                            Comment

                            Working...
                            X