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 In Reports

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

    Calculated Fields In Reports

    I have an AR module within a customer data base. I am trying to create an automated bank deposit preparation report. The report automatically grabs deposit items from a payments transaction database (matched by date), but only should grab certain types of payments (Cash, Checks, and Money Order) to print on the report. Payment types ar distinguished by a payment type field in the payments DB, and filtered by an expression on the report (i.e. Payment_Type="MOR".or.Payment_Type="CSH".or.Payment_Type="MOR"). This works fine on the surface, and the report only prints the transactions that match the expression criteria (i.e. the report does not print payments types "BTU", or "PST", or "CRDT")

    The Problem comes with the calculated summary fields on the report. When I try to use calculated fields on the report (to give a transaction count, and total), the calculated fields are including transactions that are filtered out by the report criteria. The report's calculated fields include data from records that do not print on the report itself. So I end up with a page with 3 transactions printed (i.e. the 3 that match the filter criteria for the report), but below that a report calculated field that shows 5 deposit items (i.e. counting 2 that are filtered out on the report), and a total that does not match (again counting records that should be filtered out by the report filter expression).

    Any ideas?

    #2
    RE: Calculated Fields In Reports

    Hi Mike,
    Are you using GRAND as your group, or your GROUP group (the date field?) in the count and total? Your expression should be totaling the group, not the grand level.

    I don't at all understand how or why records are being printed on the report that have been filtered out. If they are printing, then they haven't effectively been filtered out.

    Also, try RUNCOUNT(fieldname) for your running count. I haven't worked with it for awhile, so if you run into a snag, post it and I'll find an example.

    Wanda

    Comment


      #3
      RE: Calculated Fields In Reports

      You can define a calc field such as
      If(expression=.t.(or whatever), value, O) where expression is the filter. Then do a total on this. You will thereby eliminate the filtered values.

      Russ

      Comment


        #4
        RE: Calculated Fields In Reports

        And if you modify that expression slightly

        You can define a calc field such as
        If(expression=.t.(or whatever), 1, O)

        and total that calc field, you have a count of filtered items.
        There can be only one.

        Comment


          #5
          RE: Calculated Fields In Reports

          Mike,

          As an alternative to the good answers already suggested, you could export only those records you want to a temporary table, and print the report from that table. Just remember to Zap (empty) the table every time you do a new export.

          "Export, sort, and report", says Barry Rochford. He should know, he has been doing it for a number of decades ( I think he started when he was about 5 (grin).

          Jay Talbott
          Jay Talbott
          Lexington, KY

          Comment


            #6
            RE: Calculated Fields In Reports

            Thank you everyone for all your excellent feedback. I learned a lot of stuff for future reference, and ultimately came to the conclusion that I was going about the report the wrong way. I was trying to merge 3 different sub-reports (from each transaction database) into a single deposit summary report. I was far better off using groups. Used the grouping concept, the totals started working perfectly. I am still convinced there is a solution to do it the other way, but I was making it too complicated for myself. Anyway, great feedback. I have a solution that is working now. Thank you all so much for your tips.

            Comment


              #7
              RE: Calculated Fields In Reports

              Hi Mike,
              Glad you found a solution. Thanks for letting us know.
              Wanda

              Comment

              Working...
              X