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

Converting Field rule from A4 to A5

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

  • Converting Field rule from A4 to A5

    Converting from Alpha4, V7 to Alpha5, V9. Need help in converting this field rule.

    Parent=OP_CKHDR
    Field Type Width Decimal Places

    1. NUMBER C 8
    2. DATE D 8
    3. BILLCODE C 10
    4. NAME C 40
    5. AMOUNT N 10 2

    Child=DETAIL
    Field Type Width Decimal Places
    2. NUMBER C 8
    9. ACCTCODE C 15
    10. DESC C 40
    11. TAXABLE C 1
    12. AMOUNT1 N 8 2

    Field rule forOP_CKHDR->AMOUNT (Field 5)
    Type : Numeric
    Value : Summary
    Summary of : DETAIL->AMOUNT1
    Summary function : Total
    Ignore Mode : None
    Posting : Yes
    Auto Advance : No

    Tried total(Ck_Detail->Amount1,grp->ckhdr) and it works in the Expresion Builder but get the following error when I try to save.
    "Cannot use function in this context" I need this value stored in the Parent Amount field.
    Thank you in advance.

  • #2
    Re: Converting Field rule from A4 to A5

    This function is a report writer function, not intended for table level field rules or other expressions. While the function may perform in some areas outside of the report writer, its use there is not supported.
    You'll have to convert to a tablesum() or dbsum() expression.

    I can't tell if your child table is "Detail" or CK_Detail".

    Try
    tablesum("Ck_Detail","Number = "+quote(Number),"Amount1")
    or
    tablesum("Detail","Number = "+quote(Number),"Amount1")

    ass appropriate.
    Last edited by Stan Mathews; 01-20-2012, 04:41 PM.
    There can be only one.

    Comment


    • #3
      Re: Converting Field rule from A4 to A5

      Thanks for the help. Think my problem was my child was named Ck-detail. I renamed to Ck_detail and it works. Alpha must not like the -.

      Comment


      • #4
        Re: Converting Field rule from A4 to A5

        Alpha must not like the -.
        Indeed not. How would Alpha decide if you were subtracting the values in two fields/tables or referring to a hypenated table name? Best to refrain from using punctuation in a name, underscores if you feel you must punctuate.
        There can be only one.

        Comment


        • #5
          Re: Converting Field rule from A4 to A5

          Last post was in 2008, have never been able to convert my app to Alpha5! Give up then try again, give up---. Now can not get simple things to work.
          Set called Register

          Parent is Header with these fields
          Number, C, 8
          Hdrdate, D, 8
          name, c, 8
          hdramt, n, 8, 2

          Child is Detail with these fields and linked many to one by Num
          Num, c, 8
          detdate, d, 8
          unit, c, 8
          detamt, n, 8, 2

          field rules set detail fields detdate and unit to Header fields Hdrdate and Name. Works great in Alpha 4 but not in Alpha 5

          Comment


          • #6
            Re: Converting Field rule from A4 to A5

            Works great in Alpha 4 but not in Alpha 5
            Correct, V5 and later do not have field rules for sets. You should be able to create a posting field rule to do that.
            There can be only one.

            Comment


            • #7
              Re: Converting Field rule from A4 to A5

              I started with A3 back in the 80's advanced through the Alpha 4's, currently using Alpha4v7. It was never too bad converting until Alpha 5. I have Alpha 5V11 but I just can't get the hang of it. I have written most of the reports etc but it just seems like a different beast than A4. This is what I use it for....I have a trucking company. I copy last months data base into a new data base and empty it. I enter 800+ loads...date, BL #, to, from, product, wt, rate, driver #. My reports take this info and produce an invoice by custormer and a report by driver...in order to pay them. Each month I just made a new data base. As I mentioned in A4 I just clicked on utilities, copy data base, entered the new name and all my reports and designed transferred. It is probably easy in A5 but I'm just not getting it. Wish there was a way to get some specific help to get the entire conversion done for less than $10,000.

              Comment


              • #8
                Re: Converting Field rule from A4 to A5

                Originally posted by Stan Mathews View Post
                Correct, V5 and later do not have field rules for sets. You should be able to create a posting field rule to do that.
                Was doing a search about field rules and I came across this post. In version 11, Alpha will let you create a field rule for a set although those rules are stored only in the table not the set. In the builder for a calculated rule you can select fields from different tables and then Alpha converts the expression. Which is probably not the best way to do this, since we can now create field rules that are form specific. But it did work when I tried it.

                In the builder my expression initially looked like this:
                IF(DATE()-EMPLOYEE->HIREDATE >= 90,24,ROUND(TOT_HRS/30,2))

                And then Alpha converted it to this:
                IF(DATE()-LOOKUPD("F",FILENO,"Hiredate","employee","Fileno") >=90,24,ROUND(TOT_HRS/30,2))

                I am curious if anyone else has tried this...the link in my set was FILENO.
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment


                • #9
                  Re: Converting Field rule from A4 to A5

                  Possibly a question of semantics. In Alpha 4 and earlier as I understand, you could build field rules for a set stored in the set definition. With Alpha 5 and later all field rules became table based. You can build a field rule such as

                  IF(DATE()-LOOKUPD("F",FILENO,"Hiredate","employee","Fileno") >=90,24,ROUND(TOT_HRS/30,2))

                  but it has nothing to do with the set. That expression doesn't care whether the employee table is part of a set or not and will work if the employee table is dropped from the current set. I do find it quite helpful that the expression builder for a set allows one to specify multiple tables from the set and then converts portions involving child tables to expressions independent of the set.
                  There can be only one.

                  Comment


                  • #10
                    Re: Converting Field rule from A4 to A5

                    I did miss that ability to have set based field rules - why do you suppose that changed?
                    Robin

                    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                    Comment


                    • #11
                      Re: Converting Field rule from A4 to A5

                      Originally posted by MoGrace View Post
                      I did miss that ability to have set based field rules - why do you suppose that changed?
                      Data inconsistencies.
                      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.

                      Comment


                      • #12
                        Re: Converting Field rule from A4 to A5

                        https://free-lancer2.com/
                        We offer a conversion service.
                        Ted Giles
                        Example Consulting - UK
                        .

                        sigpichttp://ec12.example-software.com//
                        See our site for Alpha Support, Conversion and Upgrade.

                        Comment


                        • #13
                          Re: Converting Field rule from A4 to A5

                          dos to windows? I personally try to figure out what the FR was for and what it did and then create my own to do what was intended
                          Dave Mason
                          dave@aldadesktop.com
                          Skype is dave.mason46

                          Comment

                          Working...
                          X