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



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

Summary Operation vs xBasic tbl.summarize()

  • Filter
  • Time
  • Show
Clear All
new posts

  • Summary Operation vs xBasic tbl.summarize()

    We have a curious situation here. We have been running a tbl.summarize() piece of code for years. I needed to make some changes to the table structure, and now, it seems that the xBasic code doesn't seem to want to work. I have a summarize operation that works, and creates the appropriate records in the summary table. We needed to create the xBasic option because we need to pass a variable into the filter, and the operation doesn't afford us the option of having variables (as far as I know). What is even more curious is that if I convert the operation to xBasic using the "XB" on the toolbar, it created the exact code I had in my script, however, it doesn't summarize the data.

    this is the code;
    'from the interactive window
    dim pmtdate as D = {12/21/2017}
    filter = replace_parameters("(isblank(\"GAAS\").or.GAAS=\"N\").and.G09_ISS_DT=ALLTRIM(REMSPECIAL(DTOC([varD->pmtdate]))).AND.RELEASE=\"Y\".AND.(Rec_Type = \"EA\".or.(Rec_Type = \"TRA\".and.substr(G09_ISS_DT,3,2)<>\"01\")).AND.APPEND_DATE={}",local_variables())
    = (isblank("GAAS").or.GAAS="N").and.G09_ISS_DT=ALLTRIM(REMSPECIAL(DTOC({12/21/2017}))).AND.RELEASE="Y".AND.(Rec_Type = "EA".or.(Rec_Type = "TRA".and.substr(G09_ISS_DT,3,2)<>"01")).AND.APPEND_DATE={}
    'now the code from the script...
    	'build the filter using the date variable
    	filter = replace_parameters("(isblank(\"GAAS\").or.GAAS=\"N\").and.G09_ISS_DT=ALLTRIM(REMSPECIAL(DTOC([varD->pmtdate]))).AND.RELEASE=\"Y\".AND.(Rec_Type = \"EA\".or.(Rec_Type = \"TRA\".and.substr(G09_ISS_DT,3,2)<>\"01\")).AND.APPEND_DATE={}",local_variables())
    	a_tbl ="daily_supsvc")
    	sum.db = "dimps_sum2.DBF"
    	sum.db_dd_delete = .T.
    	sum.order = "G01_CASE"
    	sum.filter = filter 
    	'sum.filter = "(ALLTRIM(GAAS)=\"\".OR.GAAS=\"N\").AND.G09_ISS_DT=REMSPECIAL(DTOC({12/21/2017})).AND.RELEASE=\"Y\".AND.(REC_TYPE=\"Ea\".OR.(REC_TYPE=\"Tra\".AND.SUBSTR(G09_ISS_DT,3,2)<>\"01\")).AND.APPEND_DATE={}"
    	sum.options = "I"
    	sum.fields = 5
    	sum.field1 = "G01_Case"
    	sum.code1 = 0
    	sum.field2 = "G01_Case"
    	sum.code2 = 2
    	sum.field3 = "G10_Ck_Amt"
    	sum.code3 = 1
    	sum.field4 = "val(substr(G01_Case,2,6))"
    	sum.code4 = 1
    	sum.field5 = "Seq_No"
    	sum.code5 = 6
    I've also attached a picture of the operation with it's filter.

    If anyone sees something glaring, please let me know.


    Attached Files

  • #2
    Re: SUmmary Operation vs xBasic tbl.summarize()

    The only thing I would suggest is to restart the machine running the code. I have encountered unexplained behavior that suggested the original code was somehow held in memory and being executed rather than the altered code.
    There can be only one.


    • #3
      Re: SUmmary Operation vs xBasic tbl.summarize()

      Are you closing a_tbl after the op runs in your script?

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


      • #4
        Re: SUmmary Operation vs xBasic tbl.summarize()

        Stan, Did that to no avail.

        Robin, Yes, we did close the table.

        ISSUE Resolved.

        I checked another application that produces the same basic end result and saw that we were using a variable in the filter of the summary operation. We just declared it as a global in the script beforehand.

        I declared a global variable "pmtdate" in the IW, then edited the operation, placing the variable in the summary folder, and MAGIC, it worked!!!

        This is much cleaner than modifying code, and best of all, it works. I'm still stymied by the problem, but we REALLY needed to get this working as it's been down for over a week.
        This process produces a text file in a specific format for another program to use the text file as input to an OLD mainframe application. The outcome of it is that we (the state) are paying clients or vendors for specific types of assistance. The run I did this morning was for over 40K, so you can see that it is kind of important that it works.

        Thanks, for looking.

        Have a great holiday!



        • #5
          Re: SUmmary Operation vs xBasic tbl.summarize()

          What about the variable 'filter' is that global as well? I wouldn't think pmtdate needs to be global since you are using replace_parameters to set the value beforehand.

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


          • #6
            Re: SUmmary Operation vs xBasic tbl.summarize()


            I put the entire expression from "filter" into the record selection filter of the operation. Never really thought about leaving it out of the expression and just declaring the "Filter" as a global...