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

Mask XDialog Input

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

  • Mask XDialog Input

    Is there a way to mask Xdialog input
    for the code below I want the (-) dashes to be like a field rule mask

    the user would enter 0511110
    and it would be formatted in the xdialog so the user would see
    05-1111-0

    Thanks
    Charlie Crimmel

    dim global vempnum as c
    trace.clear()
    'Prompt for any ASK variables in filter/order expressions......
    ask_vars = <<%list%
    Askc_Enter_empnum
    %list%
    prompt_result = a5_prompt_for_ask_vars(ask_vars,session_variables(session_get()))
    if prompt_result <> "OK" then
    end
    else
    var->vempnum=Askc_Enter_empnum
    trace.WriteLn("empnum = " + var->vempnum)
    end if
    Last edited by Al Buchholz; 07-29-2017, 05:02 PM.

  • #2
    your answer is in the help files

    I did a simple search on xdialog, scrolled down the list which is alphabetical and found: Mask

    http://support.alphasoftware.com/alp...alog_Field.htm

    Good luck
    Cheryl
    Cheryl
    #1 Designs By Pagecrazy
    http://pagecrazy.com/

    Comment


    • #3
      Thanks, but not exactly what I am trying to do.
      If I use UI_Get_text
      the format below puts the dashes in so the user does not have to type them
      I would like the xdialog to do the same.

      text_string = ui_get_text("empnum", "Enter Employee Number for Selection"," ","&&-&&&&-&")
      IF text_string = " " THEN
      ui_beep()
      ui_msg_box("empnum", "Employee Number invalid.")
      END
      ELSE
      var->empnum = text_string
      END IF

      Comment


      • #4
        'declare vars for use in the dialog
        dim global vcgSSno as C
        vcgSSno = space(11)

        ssnum = ""

        {sp=5} Enter Social Security Number: |[11.15ssnum!ssnum_killfocus]| 9 digits, no hyphens ;
        {lf};

        case "ssnum"$ui_dlg_ctl_current("Create a New Accession Case") 'ssnum Textbox has focus
        if a_dlg_button = "enter" then 'force focus to move to &OK control,
        a_dlg_button = ""
        vclSsNum = remspecial(ssnum)
        if len(alltrim(vclSsNum))=9 then
        ssnum = left(vclSsNum,3) + "-" + substr(vclSsNum,4,2)+ "-" + right(vclSsNum,4)
        sys_send_keys("{TAB}")
        end if
        elseif a_dlg_button = "ssnum_killfocus" then 'insert the hyphens for the user
        'note: killfocus event fires on each keystroke
        ' while ssnum has focus
        a_dlg_button = ""
        vclSsNum = remspecial(ssnum)
        if len(alltrim(vclSsNum))=9 then
        ssnum = left(vclSsNum,3) + "-" + substr(vclSsNum,4,2)+ "-" + right(vclSsNum,4)
        end if
        end if
        Cheryl
        #1 Designs By Pagecrazy
        http://pagecrazy.com/

        Comment


        • #5
          I am able to format the user input
          The same concept works for ssn and phone numbers
          Thanks

          trace.clear()
          dim global empnum as c
          var->empnum=""
          Result = ui_dlg_box("EMPNUM",<<%dlg%
          {region}
          EMPNUM:| [.30empnum!empnum_*]
          {endregion};
          {region}
          <*15&OK> <15&Cancel>
          {endregion};

          %dlg%,<<%code%
          '----------------
          if len(alltrim(empnum))= 2 then
          first2 = substr(empnum,1,2)+"-"
          var->empnum = first2
          end if
          if len(alltrim(empnum))= 7 then
          second4 = substr(empnum,4,4)+"-"
          var->empnum = first2+second4
          end if
          if len(alltrim(empnum))= 9 then
          third1 = substr(empnum,9,1)
          var->empnum = first2+second4+third1
          end if

          '----------------
          if a_dlg_button = "&OK" .or. a_dlg_button = "&Cancel" then
          trace.WriteLn("EMPNUM = " + var->empnum)
          'do nothing, dialog will close
          else 'the event has not been handled, so set a_dlg_button to "" to keep the dialog open
          a_dlg_button = ""
          end if
          %code%)
          end

          Comment


          • #6
            Re: Mask XDiaglog Input

            I have a similar problem.
            How to mask form field based on character variable.
            Display must look like : 199-007-07.
            We want to ensure that the user do not have to type the dashes (-).
            Dragan Milosavljevic
            ITPartner

            dragan.milosavljevic@itpartner.rs
            http://www.itpartner.rs

            Comment


            • #7
              Re: Mask XDiaglog Input

              Place this on the form field CanDepart event, replacing what's in red with the name of your field:

              Code:
              dim vF as C
              vF=alltrim(topparent:field1.value)
              topparent:field1.value=substr(vF,1,3)+"-"+substr(vF,4,3)+"-"+right(vF,2)
              You can do this with the mask table field rule, but I shy away from field rules.
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment


              • #8
                Re: Mask XDiaglog Input

                Using Mike's logic you could also

                Code:
                topparent:field1.value = mask(vF,"   -   -  ")
                Where the mask has three spaces, a dash, three spaces, a dash, and two spaces inside the quotes.
                There can be only one.

                Comment


                • #9
                  Re: Mask XDialog Input

                  Gotta love old threads if you can find them! Interestingly, there is not an XD smart field to help format text input like there is for dates and such
                  See: Xdialog Smart Fields.

                  Although you could use %P=ui_get_text() to add the format string - it pops up another dialog.

                  So this is my modification to see a SSN formatted as the user types it in:

                  Code:
                  dim vSSN as c
                  vssn=""
                  Result = ui_dlg_box("Format SSN",<<%dlg%
                  {region}
                  SSN:| [.20vSsn!evSsn_*]
                  {endregion};
                  {region}
                  <*15&OK> <15&Cancel>
                  {endregion};
                  
                  %dlg%,<<%code%
                  if a_dlg_button = "evssn_change" then
                  	vSSN = mask(remspecial(vSSN),"   -  -    ")	
                  end if
                  '----------------
                  if a_dlg_button = "&OK" .or. a_dlg_button = "&Cancel" then
                  trace.WriteLn("SSN = " + var->vSSN)
                  'do nothing, dialog will close
                  else 'the event has not been handled, so set a_dlg_button to "" to keep the dialog open
                  a_dlg_button = ""
                  end if
                  %code%)
                  end
                  If you add the %N% directive, the killfocus event could be used, but you would only see the change when the control loses focus. And without the %N% directive you won't see the killfocus event do anything...

                  By using the change event and remspecial() in conjunction with the mask(), the control updates properly. And now that area codes are required for dialing all phone numbers, this could easily be adapted for that use too.

                  Edit: Just noticed that Xdialog was spelled wrong - probably explains why this thread was so hard to find!
                  Last edited by Al Buchholz; 07-29-2017, 04:59 PM. Reason: fixed spelling.. for Robin.. ;)
                  Robin

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

                  Comment

                  Working...
                  X