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

Calculation Help

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

  • Calculation Help

    I'm hoping that this is simple, but I just can't seem to get past it.

    We have an employee system where there is an employee table and attached to it is a position history "Child" table. We are trying to develop a report where we show the current title (that one is easy) and the first time the employee was "permanent". That is designated by a date in a field called "From" and a code of "RA" in a "status" field of the child record. Some employees have been here many years, so there are many Child records.

    What I am trying (unsuccessfully) to do is to get the first non-blank calc field "PERMANENT". I'm going around in circles.

    Here are the calcs:

    Code:
    firstperm	if(calc->Permanent="".and.calc->Firstperm="","",calc->Permanent)
    lasttitle	last(Titles->Title,GRP->Lfname)	
    PERMANENT	IF(POS_HIST->STATUS="RA", DTOC(POS_HIST->FROM), " ")	
    PROVISIONL	IF(POS_HIST->STATUS="PA", DTOC(POS_HIST->FROM), " ")	
    realfirsrt	if(calc->Firstperm<>"",calc->Firstperm,calc->Permanent)
    any thoughts would be appreciated.

    Tom:confused:

  • #2
    Re: Calculation Help

    Maybe

    TABLEMIN("POS_HIST","STATUS = 'RA' .AND. FROM > {01/01/1900}","FROM")

    Some employees have been here many years
    Might have to use an earlier year than 1900.

    Well, the first expression would be ok for the earliest employee. For an individual employee id.....

    TABLEMIN("POS_HIST","ID = "+quote(id)+" .and. STATUS = 'RA' .AND. FROM > {01/01/1900}","FROM")

    supplying the quoted id from the current record in the report.
    There can be only one.

    Comment


    • #3
      Re: Calculation Help

      What I am trying (unsuccessfully)
      how was it unsuccessful? Did it error due to your setting the second (false) part of the if() to a character instead of a date-- you used " " instead of {} - curly brackets which are for a empty date value.


      EDIT--which Stan's expression obviously eliminates!
      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


      • #4
        Re: Calculation Help

        Is the "RA" status field value appearing in multiple records for an employee, and you're trying to find the first one? Some sample data would help us offer suggestions.

        In the absence of sample data I'm thinking you could build a custom UDF that will open the "child" table, indexed on the employee id number. Fetch_find the first related child table record, then step through them until you find a record that has the right status value. Return the date field (or its character equivalent) from the function.

        If performance becomes an issue you could offload the desired status field values to a separate table, once, using a batch processing script, and then record first RA transactions there going forward.

        Last notion would be to reverse the table relationships in the set, and filter the primary table to only show records that have the right status field values.

        Comment


        • #5
          Re: Calculation Help

          I see Stan is suggesting something similar, but with much less coding required. Would be interesting to see if the tablemin() approach was faster than the indexed find by key sequence I described. Both will require alpha to open a new instance of the child table for each employee.

          Comment


          • #6
            Re: Calculation Help

            Thanks for all your replies.

            Stan,
            TABLEMIN() shows the first instance of the date in the table. I just need it for the subset of records pertaining to the particular employee. I even put an additional filter in your code to make it test the Employee->empID against the POS_HIST->EMPID, to no avail.

            Code:
            TABLEMIN("POS_HIST","Pos_Hist->Emp_Id=Emp_Id.and.STATUS = 'RA' .AND. FROM > {01/01/1900}","FROM")
            Mike,
            The error I was getting was that in the "firstperm" calc, I was testing the firstperm calc field, and I don't think Alpha can handle that.

            Tom,
            you gave me an idea to build another set with just "RA" type records. I'll test that out and let you know.

            To all, thanks for your suggestions.

            Tom

            Comment


            • #7
              Re: Calculation Help

              It worked here with a test variable. I would explicitly pass the emp_id value into the function.


              Code:
              TABLEMIN("POS_HIST","Pos_Hist->Emp_Id="+quote(Employee->empID)+" .and. STATUS = 'RA' .AND. FROM > {01/01/1900}","FROM")
              There can be only one.

              Comment


              • #8
                Re: Calculation Help

                Stan,

                I'll give it a whirl, thanks.

                Tom

                Comment


                • #9
                  Re: Calculation Help

                  Got it working. Thanks STAN!

                  It turned out the the field EMP_ID is numeric. That causes all sorts of issues in a character string filter.

                  Here is the code that works:

                  Code:
                  TABLEMIN("POS_HIST","Pos_Hist->Emp_Id="+val(str(Emp_Id))+".and.STATUS = 'RA' .AND. FROM > {01/01/1960}","FROM")
                  The report carries on for a little bit, but since I get the results I need, I don't care.

                  Again, Thanks.

                  Tom:)
                  Last edited by Tom Henkel; 03-01-2011, 12:44 PM. Reason: can't type

                  Comment


                  • #10
                    Re: Calculation Help

                    We should be able to speed it up using dbmin() rather than tablemin() but I'll have to work on that. Michael Humby showed me how one time but I've never utilized it.

                    It was dbsum() that I was remembering. Don't see how to make it work with dbmin().

                    The filter for the tablemin() could use isdate() to invalidate the blank "from" values rather than that fixed method I suggested.

                    +" .and. status='RA' .and. isdate(dtoc(from))"
                    Last edited by Stan Mathews; 03-01-2011, 02:22 PM.
                    There can be only one.

                    Comment

                    Working...
                    X