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

Calc field on a report

  • Filter
  • Time
  • Show
Clear All
new posts

    Calc field on a report

    I have created a report based on a set. In the detail section I have a number of calc fields the returns an if/then value. There are only ever 10 records to the report. It works fine on the first two rows, but the last 8 rows show the same value which are wrong. Attached is picture of the report.

    Why would I get correct value in the first two records and the wrong value (which is the same in every one) in the next 8
    Mark Pearson
    [email protected]
    Youtube channel

    Re: Calc field on a report

    Not much information to work with. Does the set involve one-to-many links? If so, the calc fields in the details band get evaluated for each composite record in the set. Do the calc expressions involve fields from a "parent" table in your set? You may be getting duplicate results for the same reason you'd see duplicate field values if you dropped a field from a parent table into the details band. Perhaps review of the section on one-to-many sets in the Reports chapter of the User Guide will help you get this sorted.

    Furnish a working copy of the problem and we can check it for you.


      Re: Calc field on a report

      Thanks Tom,

      The complexity and scope of my db is such that actually posting it would probably cause more discussion than the problem.

      I think my thoughts were more concerned with why two records can be correct and the others fail. I consider that abnormal behavior. However, it was a consistent flaw (result) so I presume my setup was too complex. I think your words confirm this.

      As always when things like this happen, I look at the construct and possible work arounds. Result has been a completely different approach. Flattened the table somwhat so I did not need to have so many connecting tables in the set, then wrote a script to fill some fields and result - perfect
      Mark Pearson
      [email protected]
      Youtube channel


        Re: Calc field on a report

        While possible, I think it unlikely that the calc expressions "failed". Alpha was probably doing what you told it to, just not what you intended. Composite records in a one-to-many set will frequently produce unexpected repeating patterns in reports. Calc field that are "built on" composite records can do the same.

        In any case I'm glad you have it sorted.


          Re: Calc field on a report

          I have found that when either a filter or order (mostly) is too long and the expression builder cannot resolve it, that records will also repeat (at random many times). And I am not referring to having necessarily a filter/order that exceeds the maximum length, just one that must be a bit too complex and due to timing or whatever, fails and produces multiple records sporadically (although exceeding the limits will produce similar issues).

          The remedy?? :) Punt! I usually reduce one or both until results are as expected and then add back in, changing the one I found to be the problem causer to either something else or a preprocessed one.
          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