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
Devcon 2020 Goes Virtual! LEARN MORE >

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 on Report

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Calculated Fields on Report

    Is it possible to get a calculated field from another report as to not have to create it again? The calculated fields on a new report are blank, but of course on the finished "other" report they are available.

    Scott
    Tags: None
    #2
    Re: Calculated Fields on Report

    1. Copy and paste from one report to another.

    2. Global calculated field - table - edit structure - global calculated fields - then it's available on every object.

    3. Mapped table - allows 1 to 1 mappings - calculated fields from the mapped table(s).
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment

      #3
      Re: Calculated Fields on Report

      Al,

      I was very interested to see your comment re "Global calculated field" as in all the years I have used A5 I did not know such a thing existed. This is a real gem and I guess many do not realise (not a typo, that's how we spell it in Oz) it exists but it has real advantages as it eliminates the problems with "calculated fields" that are defined in the table structure and are not necessarily refreshed.

      To share my excitement, a simple example is say where we have an application with a PartMaster table with fields PartNum and PartDescription (it's a pity Alpha does not support camel case) and later use PartNum in many other tables (BOM lines, Invoice lines, Costing, etc.) we can define "Global calculated field" in the required table and have it available when designing forms, reports and browses to drag onto the layout as a field all ready to go!!

      It is a pity that Action Script (AS) xdialogs that contain a listview do not make "Global calculated fields" available from the list of "fields" that can be included, but I will put this in the "Features Wishlist". I will give it a few days just in case someone can tell me how to include such a "field" in a listview.

      Selwyn, please feel free to jump in and set me straight if I have missed some functionality in AS.

      Comment

        #4
        Re: Calculated Fields on Report

        Garry,

        Reference Listview. If you go to the very last post of this topic

        Listview Format

        You may be able to modify the example to create a function that would do a calc for you.

        But yes to the wish on calcs in a list view. I have moved to using the Browse in xdialog to get around a lot of the field format and calc issues. Proving to be a very useful tool
        -----------------------------------------------
        Regards
        Mark Pearson
        [email protected]
        Youtube channel
        Website

        Comment

          #5
          Re: Calculated Fields on Report

          Originally posted by Garry Flanigan View Post
          Al,

          I was very interested to see your comment re "Global calculated field" as in all the years I have used A5 I did not know such a thing existed. ....
          Al did not mention it but they can also be defined for a set: Edit Set---Set--Global Calculated Fields.

          Raymond Lyons

          Comment

            #6
            Re: Calculated Fields on Report

            If used, make sure you note it somewhere that you are using a Global calc field....awfully hard to find where to change/delete it later if you or someone else needs to modify the application!
            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

              #7
              Re: Calculated Fields on Report

              Mark,
              You mention using a browse in xdialog but I do not see this option.
              Also, does anyone know how to get the value of a "global calculated field" with xbasic?

              Comment

                #8
                Re: Calculated Fields on Report

                Gary,
                Hmm, I posted the following links last night but it looks like the post did not go through.

                The suggested global calculated 'field' is also known as a calculated value. "field' is a bit of a misnomer as it is not stored in a table.

                Calculated Values
                Calculated fields

                Also now a days there is an extra tab in the form's calculation dialog that shows the calculations that come from the table or set. The calcs are not editable from there however. And when they appear in the drag-drop list the table name is noted after the calc name.
                Tim Kiebert
                Eagle Creek Citrus
                A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                Comment

                  #9
                  Re: Calculated Fields on Report

                  Tim,
                  Thank you for links.
                  I have read these previously and have experimented with adding a global calculated field to a form. When you look at its properties thru the object explorer, its name is say calc->mycalcfield, where mycalcfield is whatever the field is named.
                  However if in the interactive window you get a pointer to the table and fetch the first record then how can you obtain the value of calc->mycalcfield? Obviously there is a way because Alpha can do it in layouts.

                  Comment

                    #10
                    Re: Calculated Fields on Report

                    Yeh, I have been thinking on that one since you asked that earlier. Although I have used global calculated 'values' plenty of times I haven't needed to access them via xbasic. ( haven't thought of it actually). If I need that calculation I just put it in the code.

                    Just investigated a bit and think maybe you can't. I believe the calcs are available through the layouts because the calc definitions are stored in the dictionaries as are the form definitions. So when you open a form the calc definition is retrieved and then the calc is done based on the tables opened by the form. In other words the calculated values are not sitting with the table waiting to be used.
                    Tim Kiebert
                    Eagle Creek Citrus
                    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                    Comment

                    Previous template Next
                    Working...
                    X