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

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

cut up a string that is in a calculated field on a report

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

    cut up a string that is in a calculated field on a report

    I have a calculated field on a report that displays a text string that shows all of the developer's sql query stuff AND all of the filters created by the user as they search a grid (thanks to Selwyn). Please see the screenshot attached.

    The filters created by the developer all seem to be within the first set of parentheses. I would like to have a second calculated field on the report that strips off the stuff in the first set of parenthesis, including the parenthesis. This is so the user will only see the search filter they applied. They don't need to see the stuff from the sql query for the report that the developer did (makes a big mess). BTW, on the report, there is another calculated field under the first one that is showing what the report is ordered by... the AP_VENDOR_CODE field... ignore that.

    I know I need to use some embedded string functions that find the index position of the first closing parenthesis and then one that slices it and everything before it. But after much searching in Alpha help, etc., I just can't find what I need.

    After being to W3 Schools page, I would think it would be something like this:

    var str = I'm being brain dead... field name that has the text is sqlfilter... hmmm, how do I refer to a field on a report in Alpha?

    str.slice(0,str.IndexOf(")"))

    Any assistance will be appreciated.
    Last edited by kingcarol; 08-11-2010, 07:01 PM.
    Carol King
    Developer of Custom Homebuilders' Solutions (CHS)
    http://www.CHSBuilderSoftware.com

    #2
    Re: cut up a string that is in a calculated field on a report

    Given how complicated the string is, maybe best to go to the wiki and see "stringscanner". It is very powerful but also see other "character comparison functions" that are generally easier to learn.

    Comment


      #3
      Re: cut up a string that is in a calculated field on a report

      In addition to what Garry said, take a look at extract_string() and substr() and the character extraction functions.
      Peter
      AlphaBase Solutions, LLC

      [email protected]
      https://www.alphabasesolutions.com


      Comment


        #4
        Re: cut up a string that is in a calculated field on a report

        Thank you, Garry and Peter. You pointed me in the right direction and I've had wonderful luck with:

        atc() to find position of the first )parenthesis
        substr() to remove string before that position
        STRITRAN() to replace words in the remaining string
        Carol King
        Developer of Custom Homebuilders' Solutions (CHS)
        http://www.CHSBuilderSoftware.com

        Comment


          #5
          Re: cut up a string that is in a calculated field on a report

          FYI, Here is the xy code for that calculated filter display field in the report header and it works perfectly. If the user applies search filters in the grid that calls a report like the one described by Selwyn in video 38 (http://news.alphasoftware.com/V10Preview/videos.htm) that reacts to those search filters, then the a5_getReportSQLFilter will capture both the developer and user filters. The developer sql filters are at the first of the string and are enclosed in parenthesis. Following the end parenthesis of the developer filters is .and. So the code below finds the position of ").and" and cuts it and everything before it out of the string to produce the sqlfilterUser calculated field. And then the rest of the code slices up the string based on other stuff to clean up in the user filter string. That would change for every report. But the first 3 lines below might work on every report. more testing to do...

          See screenshot of the report now and compare to the one I posted when I started the thread. BTW, I should mention that I am using Query By Example (qbe) for the user to filter the rows. Gets rid of having "like" in the filter string and uses simple operand like = or >=, which looks better to user.

          This code is done in the xy box for calculated fields that are used in the report header.

          Code:
          sqlfilter = a5_getReportSQLFilter(.t.)
          sqlfilterByUserTest = atc(").and.",calc->sqlfilter)
          sqlfilterUser = If(calc->sqlfilterByUserTest=0,"None.",substr(calc->sqlfilter,atc(").and.",calc->sqlfilter,1)+1))
          inlist = ".and. TblGLAllEntries.,TblGLAllEntries.,.and, 12:00:00 00 am,AP_VENDOR_CODE,JOB_CODE,GL_DATE,GL_DOCUMENT,GL_DESCRIPTION,GL_MAIN_ACCT_NUM,DEPT_ID,JOB_SUB_CODE,PAID_STATUS,PAID_DATE,PAID_CHECK_NUM,PAID_CASH_ACCT,PO_NUM,. Round((QUANTITY * AMOUNT),2)"
          outlist = "|,|,"","",Vendor,Job,GL Date,Inv Num,Description,GL Num,Dept,Cost Code,Status,Paid Date,Check Num,Cash Acct,PO Num,|Amount,:"
          inlistrows = comma_to_crlf(calc->inlist)
          outlistrows = comma_to_crlf(calc->outlist)
          sqlfilterresult = stritran_multi(calc->sqlfilterUser,calc->inlistrows,calc->outlistrows)
          sqlorder = a5_getReportSQLOrder()
          sqlorderresult = stritran_multi(calc->sqlorder,calc->inlistrows,calc->outlistrows)
          Last edited by kingcarol; 08-13-2010, 10:17 PM.
          Carol King
          Developer of Custom Homebuilders' Solutions (CHS)
          http://www.CHSBuilderSoftware.com

          Comment


            #6
            Re: cut up a string that is in a calculated field on a report

            UPDATE: Apparently something has been changed in the function a5_getReportSQLFilter. Selwyn says he hasn't changed anything, but for some reason, I no longer have to remove the search (or filter) criteria done by the developer from the resulting string, and so now can remove 2 lines of the XY code for the report as shown below.

            Code:
            sqlfilter = a5_getReportSQLFilter(.t.)
            inlist = ".and. TblGLAllEntries.,TblGLAllEntries.,.and, 12:00:00 00 am, 11:59:59 00 pm,AP_VENDOR_CODE,JOB_CODE,GL_DATE,GL_DOCUMENT,GL_DESCRIPTION,GL_MAIN_ACCT_NUM,DEPT_ID,JOB_SUB_CODE,PAID_STATUS,PAID_DATE,PAID_CHECK_NUM,PAID_CASH_ACCT,PO_NUM,. Round((QUANTITY * AMOUNT),2)"
            outlist = "|,|,"","","",Vendor,Job,GL Date,Inv Num,Description,GL Num,Dept,Cost Code,Status,Paid Date,Check Num,Cash Acct,PO Num,|Amount,:"
            inlistrows = comma_to_crlf(calc->inlist)
            outlistrows = comma_to_crlf(calc->outlist)
            sqlfilterresult = stritran_multi(calc->sqlfilter,calc->inlistrows,calc->outlistrows)
            sqlorder = a5_getReportSQLOrder()
            sqlorderresult = stritran_multi(calc->sqlorder,calc->inlistrows,calc->outlistrows)
            Last edited by kingcarol; 09-12-2010, 12:44 PM.
            Carol King
            Developer of Custom Homebuilders' Solutions (CHS)
            http://www.CHSBuilderSoftware.com

            Comment

            Working...
            X