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

Report - lookup comma separated codes

  • Filter
  • Time
  • Show
Clear All
new posts

  • Report - lookup comma separated codes


    I have a report based on a table that has a 'memo' field that contains a set of codes, e.g.


    I need the report to show the values of the codes not the codes themselves, e.g.


    Im assuming i need some sort of clever calculated field in the report. Does anyone have an example on how i would go about achieving this?



  • #2
    Re: Report - lookup comma separated codes

    The following might give you an idea--created in the interactive window....the amem variable I have here would represent your table's memo field. The variable lst would have to be created for the report layout. The red represents what you likely would use for code. I based the lookup on a table called item_lookup that has 2 fields, num_code and Item. As you did not specify exactly what you are dealing with, this is just a guess, but the code could be a basis for you to use. A bunch of other ways am sure also... my guesses are usually the first thing that comes to mind and, without knowing the exact scenario, many times are way off !! :) .
    dim amem as c
    [COLOR=Red]dim lst as c[/COLOR]
    = "Cars,Bikes,Trains,Planes"
    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


    • #3
      Re: Report - lookup comma separated codes

      The problem is that the *for_each() statement is non-functional with a calculated field. You get a "value of foo not found" error. I have found no way to capture the value of the field and run a loop function to deliver a list through lookups in a report.
      Mike W
      "I rebel in at least small things to express to the world that I have not completely surrendered"


      • #4
        Re: Report - lookup comma separated codes

        OK.thanks for your time Guys.

        I take it this cannot be done.



        • #5
          Re: Report - lookup comma separated codes

          I recommend adding the area_discipline field to the table for the report and have it populated at the time of area_discipline_id population. In this case I think you will have to break normalizing rules.
          Mike W
          "I rebel in at least small things to express to the world that I have not completely surrendered"


          • #6
            Re: Report - lookup comma separated codes

            The problem is that the *for_each() statement is non-functional with a calculated field.
            Yes, but if you create a udf that uses the *for_each() and use that udf in the calculated field..................

            As suggested here 16 days ago.
            There can be only one.


            • #7
              Re: Report - lookup comma separated codes

              Very well done! Yes, I tried to worked back and forth a UDF called from the report calculated field and could not make it work. It was one that took your original entry and separated the components to separate lines and not the succint line yours has. Yours clearly works sparkling! Thank you. This is one I will have to break down and learn from where I wasn't successful. Thank you.
              Mike W
              "I rebel in at least small things to express to the world that I have not completely surrendered"


              • #8
                Re: Report - lookup comma separated codes

                All now looks good. Thanks for all your help.