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



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

  • Filter
  • Time
  • Show
Clear All
new posts

    Field Rules

    I think that my memory is swaping out to my hard disk in my head!

    Does anyone know if you can cause a field rule to evaluate... or
    re-evaluate from a fields event for the current record?

    I have a tabbed object on a form that seperates fields in a table to
    conserve space. There is a field rule that sets a default value
    for one of the fields on the 2nd tab. When the form goes into
    enter mode the default value was not set. I changed the properties
    of the field rule to set the value at the beginning of the data entry.
    that worked fine. I guess I am asking if 2 tabs have primary table fields,
    when you goto the next tab does the record save & put you into modeless
    entry mode. Also was wondering about the option of re-evaluating
    field rules for the current record only after the record has been saved?

    RE: Field Rules


    The default value rules fire only on entering a record. Once the record is saved it's done. You can re-evaluate rules by going into field rules and selecting "Re-evaluate" from the Field Rules drop down but, again, this will have no effect on default rules.

    If you need to populate the field with a value you can run an update on that field. If you can do this (i.e. if the field values are constant) you may want to consider using a calculated field rather than a default value.



      RE: Field Rules

      Thanks Finian,

      I guess I knew that, just needed to hear it again!


        RE: Field Rules

        hi doug,

        i am not an expert on a5v4, but with the help of many on this board
        have got me thru a lot of xbasic

        so with that in mind

        my application required a lot of fields to be set up
        as default calculations
        (pure calculated field rule would not work because user needed to be able to
        change the value)

        however if the user made a change to field that was a componant
        of the default calcualtion, it would , of course, not re-evaluate,

        again , with the boards help, someone suggested a little xbasic
        script that would do just that (re-evaluate) or i like to call it
        "tickle" the re-calc on a change
        (i can't remember who it was, but am forever grateful)

        if you still need come help on this, i can post a sample of the script
        given to me.
        it works like a charm


          RE: Field Rules


          My problem here was very minor, I was able to work through it
          very simply. Sometimes I get tunnel vision when working in
          Alpha 5, my focus gets too narrow to see what is actually happening.

          Thanks for taking time to respond to this message....I would still
          like to see your script for re-evaluating a calc field, it might
          come in handy down the road. There may be others who would find it
          useful as input is what makes this forum such a
          valued resource!

          Have a great 4th!!


            RE: Field Rules

            hi doug

            as i said, someone else made this contribution
            and am sure they will recgonise their signature on this code and
            should take full credit

            the script is attached to the field that the user can change,
            "onwrotefield -- event"
            which is a
            componant of a calculation --

            the calc is defined in the field rules
            as a "defualt", in the field "amount", price x quantity
            (not as a calculated field)
            for the field that contains the result of the calc

            in this case -- "sol3->amount" is the result of sol3->price x sol3->

            if the quantity is "changed" after an "enter", this will
            tickle the re - evaluation of the amount

            if t.mode_get()=1 then
            if a_field_value=""
            end if

            hope this helps
            i know it saved me

            i think i got a little repetative in their
            hope it's clear enough