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

forcasting

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: forcasting

    wow stan thats awsome is there a way to make a total of all field??
    https://www.housingeducator.org
    k3srg

    Comment

      #17
      Re: forcasting

      I got it wow that wan't too hard
      i just added a new cacl field and made it add the others
      I'm so hyper the boss is going to be Extremly happy.
      Thank you so much Stan
      Last edited by steve745; 10-23-2008, 09:15 AM.
      https://www.housingeducator.org
      k3srg

      Comment

        #18
        Re: forcasting

        I can't seem to reproduce the calc fields on payment keeps telling me invalid or incomplete expression, i got the vars added and when try to drag new calc field i use the expression u made and i get incomplete or invalid. am i missing something
        https://www.housingeducator.org
        k3srg

        Comment

          #19
          Re: forcasting

          Originally posted by steve745 View Post
          am i missing something
          Obviously.

          Did you make the variables session scoped? Did you check the expression carefully? You can copy and paste from this message instead of retyping.

          Code:
          AMT1 = tablesum("payments","between(Pay_date_O,{"+dtoc(Var->strt)+"},{"+dtoc(var->nd)+"}) .and. case = "+quote(case.value),"val(Pay_amount)")
AMT2 = tablesum("payments","between(Pay_date_T,{"+dtoc(Var->strt)+"},{"+dtoc(var->nd)+"}) .and. case = "+quote(case.value),"val(Pay_amoun0)")
AMT3 = tablesum("payments","between(Pay_Date_0,{"+dtoc(Var->strt)+"},{"+dtoc(Var->nd)+"}) .and. case = "+quote(case.value),"val(Pay_Amoun1)")
AMT4 = tablesum("payments","between(Pay_date_F,{"+dtoc(Var->strt)+"},{"+dtoc(var->nd)+"}) .and. case = "+quote(case.value),"val(Pay_amoun2)")
AMT5 = tablesum("payments","between(Pay_date_1,{"+dtoc(Var->strt)+"},{"+dtoc(var->nd)+"}) .and. case = "+quote(case.value),"val(Pay_amoun3)")
          There can be only one.

          Comment

            #20
            Re: forcasting

            ok i got the cacl fields and the vars but when i switch out of design mode to test it the fields still say AMT1-5 when i Change the dates nothing happens?
            is there a query i have to run to get it
            https://www.housingeducator.org
            k3srg

            Comment

              #21
              Re: forcasting

              If the fields show their names rather than values it means that Alpha can't determine the value to be displayed.


              You are adding the calc fields to the database that you originally attached with the security? Email me the login information and I'll add it there and send it back to you. You can save it to a new location and see what the difference is.

              You could just email me the whole thing, with the login information, and I'll see what is wrong.

              [email protected]
              There can be only one.

              Comment

                #22
                Re: forcasting

                You changed the pay_amount, Pay_amoun0, etc to numeric type, and that is proper. This changes the expression you need for the tablesum() parameter for the field to be summed.

                Change all the ending parts of the tablesum()'s

                "val(Pay_amount)"
                "val(Pay_amoun0)"
                ...
                "val(Pay_amoun3)"

                to

                "Pay_amount"
                "Pay_amoun0"
                ...
                "Pay_amoun3"

                since we don't need the val() function to convert the previously character field values to numbers any longer.

                Example:

                Code:
                AMT1 = tablesum("payments","between(Pay_Date_O,{"+dtoc(Var->strt)+"},{"+dtoc(Var->nd)+"}) .and. Case = "+quote(Case.value),"Pay_Amount")
                There can be only one.

                Comment

                  #23
                  Re: forcasting

                  ok i fixed the AMT1-5 when i attempt to make a calc field for total with total(amt1+am2 etc it hangs the system thinking that the computer is running the calc as i'm entering the expression. it hangs alpha and i have to force a5 closed. I have a lot of records on the dbase it like it is running a query. everything else works great.
                  https://www.housingeducator.org
                  k3srg

                  Comment

                    #24
                    Re: forcasting

                    The expression for the total would be

                    Code:
                    amtttl = calc->Amt1+calc->Amt2+calc->Amt3+calc->Amt4+calc->Amt5
                    total() is not necessary.
                    There can be only one.

                    Comment

                      #25
                      Re: forcasting

                      ok i had it work 1 time do i have to run a query of some sort prior to i keep getting 0.00 on amt1-5 no matter what i do.
                      https://www.housingeducator.org
                      k3srg

                      Comment

                        #26
                        Re: forcasting

                        No query required. The tablesum() expressions refer to the current case shown on the form (case.value).

                        I'll attach the example from your email here. Since you sent the login information directly there should be no harm in that. Actually I deleted your email message so I can't even open it any longer.

                        Got the password via private message. Calculations take place instantly in the sample. The sample had no case field values in the enrollment table and the payments table. I had to supply these for the form and the expressions to work. Without them there were no records linked to the parent in the clients table.
                        Last edited by Stan Mathews; 10-23-2008, 01:50 PM.
                        There can be only one.

                        Comment

                          #27
                          Re: forcasting

                          i'm just wondering if the amount of records i have is holding the process up i have like 300,000 records i'm going to side by side these and see what i'm F* ing up.

                          I appended all the records that are in the actual dbase and tested it doesn't gather all the infomation i have payments that i know should be in there for tommorow and it only finds a total of 1350 which isn't right i also ran it for today and i know 1 payment is scheduled and it doesn't show up. would there be need for a pause with the amount of records that i'm dealing with.
                          Last edited by steve745; 10-23-2008, 02:51 PM. Reason: typo
                          https://www.housingeducator.org
                          k3srg

                          Comment

                            #28
                            Re: forcasting

                            it appears that the problem comes in when i delete the test records and append real records it's not getting the new appened info. i've updated indexes too but nothing
                            https://www.housingeducator.org
                            k3srg

                            Comment

                              #29
                              Re: forcasting

                              Your sample had values in the case field in the clients table but none in the enrollment table and payments table. I had to put some in so it would work the way I thought you wanted. The basis of my sample is that the tablesum() functions look for records in the payments table linked to the currently visible "case", not all records in the payments table in the date range.

                              If you want that, remove the portion doing that.

                              Code:
                              AMT1 = tablesum("payments","between(Pay_Date_O,{"+dtoc(Var->strt)+"},{"+dtoc(Var->nd)+"})","Pay_Amount")
                              There can be only one.

                              Comment

                                #30
                                Re: forcasting

                                Thanks stan for the patience in giving me light to yet another way i can do things with alpha. It works great and again thank you so much.
                                https://www.housingeducator.org
                                k3srg

                                Comment

                                Previous 1 2 template Next
                                Working...
                                X