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

Calculated Fields Will Not Access Local Variables

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

  • Calculated Fields Will Not Access Local Variables

    After moving my applications from V5 to V9, I'm experiencing some odd behavior with calculated fields on forms. Suppose I have a layout variable on the form labeled "vHours". This variable name is not found anywhere else, thereby eliminating a scope problem.

    The problem: If I run the form, all goes well. But upon putting it in design mode and bringing up the calculated fields screen, a red message appears on the lower left reading Field 'var->vHours' not found. One calculated field does use "var->vHours" in its expression.

    I have tried editing the expression and replacing "var->vHours" with expressions generated by pressing V6 and selecting vHours from the list of layout variables. That doesn't change things. Oddly, if I move vHours from being a layout variable to being a session variable, all works fine.

    Thanks in advance for any ideas on the matter.

    Steve
    Last edited by Steve Andrews; 02-10-2010, 12:30 PM.

  • #2
    Re: Calculated Fields Will Not Access Layout Variables

    I have verified this possible bug using Alpha Sports. Follow these steps and see if you experience what I experience.

    1. Bring up the "Vendor Information" form in design mode.
    2. Add a LAYOUT variable to the form labeled "vVndr".
    3. Go to the Calculated Fields screen and add the field:
    VENDOR_NAME = ""
    4. With the cursor on this field, press the "Expression Builder" button.
    5. Highlight the double quotes.
    6. Select "V6 - Variables".
    7. Insert the layout variable "vVndr".
    8. See if you get the message Field 'Var->vVndr' not found.

    If you do get the message, try cancelling out of the Calculated Fields screen, changing vVndr from a layout variable to a session variable, and then reattempt the Calculated Field (Steps 3-8 above).

    I will be curious as to what other people find. Thank you.

    Steve
    Last edited by Steve Andrews; 02-10-2010, 12:30 PM.

    Comment


    • #3
      Re: Calculated Fields Will Not Access Local Variables

      Steve
      If the variable is created as Layout variable I get the "Variable not found" error.
      If the variable is created as Session variable, I do not get the error message. Not sure why.

      Comment


      • #4
        Re: Calculated Fields Will Not Access Local Variables

        Then it must be true that when Alpha evaluates all of the expressions (not allowing you to save until errors are resolved), it fails to look at layout variables. I'm surprised.

        If this is the case (and there will be no more V9 patches :(), then I will have to go through many forms to change layout variables to session variables.

        Steve

        Comment


        • #5
          Re: Calculated Fields Will Not Access Local Variables

          Bump!

          Has anyone else tried this? Also, has anyone tried this on V10? I cannot submit a bug report on V9 and I don't want to download a 30-day trial version just for the sake of submitting the report.

          Having searched the messageboard for this, I'm surprised that other people haven't run into this problem. I guess layout variables are not very popular. As I said in my previous posting, I guess I will have to live with it and use session variables from now on.

          Steve

          Comment


          • #6
            Re: Calculated Fields Will Not Access Local Variables

            Steve, I took a look and vers 10 has the same behavior. I've submitted a formal bug report.

            Comment


            • #7
              Re: Calculated Fields Will Not Access Local Variables

              Thank you, Tom!

              I'm relieved to know that it's not just something I am doing wrong and that Alpha is now fully aware.

              Steve

              Comment


              • #8
                Re: Calculated Fields Will Not Access Local Variables

                It's wierd because the "Expression Builder" dialog sees the layout var just fine, but the "Calculated Field" dialog does not. If there was going to be an issue like this I would have expected it the other way round.

                Comment


                • #9
                  Re: Calculated Fields Will Not Access Local Variables

                  I have seen this behavior since I started with Alpha and just figured it to be the way it was....that a calculated field was "outside" of the form and so a minimum of a session (shared) variable was needed. I will be interested in the outcome of this for sure.

                  Another variance I have noticed at times is that the order within the calculated dialog box (the XY icon) plays a part lately while I did not notice this prior to version 9 ....that for calculations that depend upon prior calculations they sometimes have to be placed after them (but not always). If not, then errors occur and relocating them "fixes" them.
                  Mike
                  __________________________________________
                  It is only when we forget all our learning that we begin to know.
                  It's not what you look at that matters, it's what you see.
                  Henry David Thoreau
                  __________________________________________



                  Comment

                  Working...
                  X