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 quantity field in a table which contains stock item lines on a docket - and I have set the Field Rules - Posting tab - to subtract this quantity from the Qty Available feild in the main Stock master file.

    Works fine - subtracts OK, adds back in when deleted etc.

    However I have written some xbasic code (see below) that creates item line records automatically if the user selects a "kit" which already has all stock lines selected - to save a lot of data entry. The form has an embedded browse for the stock lines and this is automatically filled in and displayed OK.

    The automatically created stock item lines in the data table look fine - except that the quantity "postimg" rules do not happen - the stock quantity field is not updated at all. It only works when the data is manually entered.

    Any suggestions as to why?
    -----------------------------------------------------

    Code that 'auto-creates' the stock lines that belong to a kit :-

    t3.fetch_first()
    WHILE .NOT. t3.fetch_eof()
    t2.enter_begin()
    t2.docket=t1.docket
    t2.stock=t3.stock
    t2.quantity=t3.qty
    t2.enter_end(.T.)
    t3.fetch_next()
    END WHILE


    thanks

    #2
    RE: Field Rules - Posting

    Jenny,

    I am not sure if this will resolve your issue or not, but when using xbasic to populate or change record data in a table, the field rules normally do not function. Try putting a 't' in the () for the table that has the posting rule.

    t2.enter_begin(t)

    I know this works for me with many of my field rules, however I have not tried it with a posting rule.

    If this is not possible I am sure somebody else will have an alternative for you ... such as manually adding your posting rule to your xbasic code itself.

    Good luck
    Cheryl
    Cheryl
    #1 Designs By Pagecrazy
    http://pagecrazy.com/

    Comment


      #3
      RE: Field Rules - Posting

      Hi Cheryl

      just tried

      t2.enter_begin(t)

      and got error message

      variable "t" not found

      thanks Jenny

      Comment


        #4
        RE: Field Rules - Posting

        Cheryl

        just tried it with .t.

        e.g. t2.enter_begin(.t.)

        but that doesn't enforce the posting rule either.

        Perhaps I will have to manually code in xbasic.

        thanks for your help
        Jenny

        Comment


          #5
          RE: Field Rules - Posting

          Jenny,

          Sorry for not giving you the proper '.t.', did not mean to make you work harder. I was assuming that t2 was the table that has the posting rule. If my assumption is wrong and t2 is not the table that has the posting rule in the field rules, then it won't work. You need to put the (.t.) in the table that has the posting rule. Basically the (.t.) enforces the field rules for that table.

          I have an archive function and an audit function that I implement in the field rule record events that will not work when I use xbasic code to populate the table. For me this is because my functions are designed to use the field rules so if I use xbasic code to populate the table I have to manually code my archive and audit trails for that particular entry as the field rules will not work.

          You may have to do the same thing ... unless somebody else knows how to make the posting field rule fire for you.

          Good luck
          Cheryl
          Cheryl
          #1 Designs By Pagecrazy
          http://pagecrazy.com/

          Comment


            #6
            RE: Field Rules - Posting

            Jenny,

            "but that doesn't enforce the posting rule either.
            Perhaps I will have to manually code in xbasic."

            If I remember correctly, posting rules are not triggered by processes scripted in xbasic so you will have to script your own.

            Perhaps others will verify my recollection. The place to find this would probably be the A5V5 forum.

            Meanwhile, assuming you would have to script your own posting rule check out the tbl.post() method which should ease your pain.

            But before you go this route verify that
            tbl.enter_begin(.t.)
            won't do the trick.

            The logical argument specifies that field rules be enforced so perhaps you can force A5 to do the post for you after all.

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: Field Rules - Posting

              If your table pointer is based on the current form, field rules are supposed to work.
              t = table.current()
              t.enter_begin(.t.)

              UI type rules, like capitalization, never work from xbasic.

              However if you get a pointer by
              t = table.open("mytable")

              Then field rules are not in effect with the exception that calculated rules and autoincrement rules are enforced.

              Bill.

              Comment


                #8
                RE: Field Rules - Posting

                Bill

                many thanks for your help

                regards
                Jenny

                Comment


                  #9
                  RE: Field Rules - Posting

                  Jenny,

                  I remember reading about enforcing field rules in Xbasic. I found the following in the help files:

                  TABLE.OPEN()

                  If you use the .ENTER_BEGIN() or .CHANGE_BEGIN() methods to do data entry into a table opened with the TABLE.OPEN() method, not all field rules are in effect. Engine level field rules, such as auto-increment, and validation expressions are enforced. However, user interface level field rules, such as Lookups and case conversion are not enforced. If you want all field rules to be enforced, you should open a form based on the table (you can use the FORM.LOAD() method to open the form invisibly) and then use form methods to enter data.

                  The (.T.) is another reference:

                  _TBL_.ENTER_BEGIN()

                  Hope this helps,
                  Jerry Gray

                  Comment

                  Working...
                  X