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

xDialog Check Box for Unique List

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

  • xDialog Check Box for Unique List

    Hi,

    I'm trying to create an xDialog window to select unique values from a table for a Check Box - List Box.

    I don't see this option in the setup genie; or is it there and I'm missing it.

    I see all values, but I only want to see unique ones.

    Should I be doing a query first, then hand-off the table to the xDialog?

    Thanks,

    ~ Tom

  • #2
    Re: xDialog Check Box for Unique List

    Off the top of my head, create your base filter in the setup genie and then click "Add condition". This will throw you into the expression creation window. Add ".AND.unique_key_value()" to the expression, then save and you should get what you want.
    Finian

    Comment


    • #3
      Re: xDialog Check Box for Unique List

      Image 1.png
      There can be only one.

      Comment


      • #4
        Re: xDialog Check Box for Unique List

        Stan - the picture says it all. There is was, and I missed it.

        and the code added was that which Finian suggested, ".AND.unique_key_value()"

        Thank you both.

        ~ Tom

        Comment


        • #5
          Re: xDialog Check Box for Unique List

          One more question (always one more!)

          In the background of the image that Stan attached above, is an expression to hold the "Field or expression to display".

          How does one show an expression to display and another expression to capture?

          In my situation I want to display a Staffname field, but want to capture the Staffid field.

          I can add the two together using the "|" in an expression, but when I do that I cannot separate out just the staffid field.

          Another checkbox (I hope) or ???

          Thanks again,

          ~ Tom

          Comment


          • #6
            Re: xDialog Check Box for Unique List

            I don't see a built in way to do that.

            You are capturing the result of the xdialog selection to a variable? You could capture the xbasic of the xdialog and add the code (at the end). The xbasic captured should end with

            %dlg%)

            the replacement

            Code:
            %dlg%,<<%code%
            if a_dlg_button = "OK"
            your_variable = word(your_variable,2,"|")
            end if
            %code%)
            This would change the variable's contents to the second column only.

            If you don't want the staffid visible in the xdialog you can make the expression

            Code:
            Staffname+"|              "+Staffid
            and adjust the width of the variable displayed. You would also need to change to your_variable = alltrim(word(your_variable,2,"|")).
            Last edited by Stan Mathews; 02-06-2018, 12:48 PM.
            There can be only one.

            Comment


            • #7
              Re: xDialog Check Box for Unique List

              Hi Stan,

              Thanks for taking a look at this. I just can't get it to work. I've added the code above to different places without success.

              The output I need is a string I can use to print reports; e.g. 00001 00002 00003 00004

              Thanks much Stan.

              ~ Tom

              Code:
              DIM SHARED v_pteid as C
              DIM SHARED varC_result as C
              auto_list_v_pteid = table.external_record_content_get("staff","trim(Fullname)+\"|\"+space(50)+Staffid","fullname","quitdate={}")
              
              Dim format as p 
              Format.tab_stops=""
              Format.odd_row_color="White"
              Format.even_row_color="Blue White"
              Format.odd_selected_color="Dark Blue"
              Format.even_selected_color="Dark Blue"
              Format.font="Arial,10"
              Format.font_color_unselected="Black"
              Format.font_color_selected="White"
              Format.lastbutton="OK"
              Format.group_size=1
              Format.number_rows=.f.
              Format.alternating_bands=.t.
              
              'Apply 'owner draw' formatting information to the list
              auto_list_v_pteid = a5_owner_draw_list_fmt(auto_list_v_pteid,Format)
              		
              temp_count = w_count(auto_list_v_pteid,crlf())
              DELETE a_v_pteid
              DIM a_v_pteid[temp_count] as c
              a_v_pteid.initialize(auto_list_v_pteid)
              ok_button_label = "&OK"
              cancel_button_label = "&Cancel"
              varC_result = ui_dlg_box("Select Staff",<<%dlg%
              {region}
              {Region}
              ;
              {Endregion};
              {Region}
              :| [%d;O={@@}%.40,20v_pteid^$$a_v_pteid];
              {Endregion}; 
              {Region}
              ;
              {Endregion};
              {line=1,0};
              <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>;
              {endregion};
              %dlg%)
              
              v_pteid = strtran(v_pteid,crlf()," ")
              
              ui_msg_box("Variable",v_pteid)
              END

              Comment


              • #8
                Re: xDialog Check Box for Unique List

                Now I'm wondering if we need the "|" in the expression.

                Would it be any simpler to use the following just to get the Staffid out of sight.

                Code:
                auto_list_v_pteid = table.external_record_content_get("staff","trim(Fullname)+space(50)+Staffid","fullname","quitdate={}")
                ~ Tom

                Comment


                • #9
                  Re: xDialog Check Box for Unique List

                  Yours did behave differently, as if the | wasn't part of the return value.

                  Try this in your code.

                  Code:
                  v_pteid_tmp = *for_each(sid,word(sid.value,-1," "),v_pteid)
                  v_pteid_tmp = remove_blank_lines(v_pteid_tmp)
                  v_pteid_tmp = crlf_to_comma(v_pteid_tmp)
                  v_pteid = v_pteid_tmp
                  ui_msg_box("Variable",v_pteid)
                  There can be only one.

                  Comment


                  • #10
                    Re: xDialog Check Box for Unique List

                    You are likely correct, there is no reason to have columns (|) if you are going to not have them visible. With my locally constructed test the return value of the selection included the | so it was a convenient separator to pluck the staffid off the end of the return.
                    There can be only one.

                    Comment


                    • #11
                      Re: xDialog Check Box for Unique List

                      FANTASTIC - WORKS JUST AS I WANTED

                      The magic is in this line: v_pteid_tmp = *for_each(sid,word(sid.value,-1," "),v_pteid)

                      Since it takes the last word, it works with or without the "|"

                      I would have never figured that out.

                      Thanks again,

                      Smiling Tom

                      Comment


                      • #12
                        Re: xDialog Check Box for Unique List

                        I don't suppose it would ever be possible to have a person where the staffid has not been assigned? The code would then return their last name which might cause problems.
                        There can be only one.

                        Comment


                        • #13
                          Re: xDialog Check Box for Unique List

                          Tom,

                          Now I'm wondering if we need the "|" in the expression.
                          {Region}
                          :| [%d;O={@@}%.40,20v_pteid^$$a_v_pteid];
                          {Endregion};
                          This owner-draw box will work with " {data= + key_id +} ".

                          This list Box can work with as Stan mentioned.
                          {Region}
                          :| [.40,20v_pteid^$$a_v_pteid];
                          {Endregion};

                          Comment

                          Working...
                          X