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

invalid date trapping in xdialog

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

    #16
    Re: invalid date trapping in xdialog

    Martin,

    Notice the slight difference in these two lines which seems to not affect the end result. I think because that is just supplying the current value into the date picker. Both will supply a character value.

    Code:
    From:| [%DATE;P=popup.calendar([COLOR=Red]bdateC[/COLOR]);I=popup.calendar%.20bdateC!bdateC_*];
    Thru:| [%DATE;P=popup.calendar([COLOR=Red]dtoc(edate)[/COLOR]);I=popup.calendar%.20edateC!edateC_*];
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    Comment


      #17
      Re: invalid date trapping in xdialog

      Yes - I caught and corrected - it prevented using the calendar
      I think my last correction should be a keeper for a quick date range selector

      thanks again a million
      Cole Custom Programming - Terrell, Texas
      972 524 8714
      [email protected]

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment


        #18
        Re: invalid date trapping in xdialog

        Your welcome. :)

        Code archive entry maybe???
        Tim Kiebert
        Eagle Creek Citrus
        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

        Comment


          #19
          Re: invalid date trapping in xdialog

          good idea - I made 2 more small changes

          msgbox("","Invalid Date!")
          bdatec=""
          ui_dlg_ctl_goto("Enter Dates","bdate")


          msgbox("","Invalid Date!")
          edatec=""
          ui_dlg_ctl_goto("Enter Dates","edate")

          this removes the invalid date and makes it easy for them to hit the cancel button or whatever
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #20
            Re: invalid date trapping in xdialog

            Originally posted by martinwcole View Post
            Thanks Gabe,

            but I think it’s a lost cause - i.e., I can trap and warn, and go back, but I can't also let a blank one through
            After reading your post got some ideas and tried many iterations, but all failed to both capture an invalid AND let a blank through
            Perhaps I didn't decipher that part of your question. I take it you want to:
            1-If the date is blank, let it be
            2-Otherwise, if a date is entered by some means or another , check for its validity.
            All you have to do is slightly modify the code to first check for balnk, then check for validity:
            Code:
            if left(a_dlg_button,6) = "bdate_" then 
             if a_dlg_button = "bdate_killfocus" then 
            if bdate={}
            bdate={}
            else
              bdate = ctod(dtoc(bdate))
              if bdate={}
               msgbox("","Invalid Date!")
              end if   
             end if 
             a_dlg_button = ""
            end if

            Comment


              #21
              Re: invalid date trapping in xdialog

              thanks Gabe, check out and try my next to last post with changes from my last post
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment


                #22
                Re: invalid date trapping in xdialog

                I'm hoping that is not your keeper Martin. If you enter an inappropriate date, the cancel button will not get you out of it. Then pressing the red "X" closes the dialog and places you into an endless loop of message dialog the requires you to ctrl-alt-delete and close the app. Needs some work yet....

                Later:
                The changes you added in post #19 cleared the issue.
                Last edited by Mike Wilson; 07-30-2010, 09:17 PM.
                Mike W
                __________________________
                "I rebel in at least small things to express to the world that I have not completely surrendered"

                Comment


                  #23
                  Re: invalid date trapping in xdialog

                  my last one will - check it out:


                  Code:
                  'Date Created: 30-Jul-2010 07:22:26 PM
                  'Last Updated: 30-Jul-2010 07:32:17 PM
                  'Created By  : martin cole
                  'Updated By  : martin cole
                  DIM SHARED bdateC as C
                  dim shared bdate as D
                  DIM SHARED edatec as c
                  DIM SHARED edate as D
                  DIM SHARED varC_result as C
                  ok_button_label = "&OK"
                  cancel_button_label = "&Cancel"
                  varC_result = ui_dlg_box("Enter Dates",<<%dlg%
                  {Background=#237+232+211}
                  {region}
                  From:| [%DATE;P=popup.calendar(bdateC);I=popup.calendar%.20bdateC!bdateC_*];
                  Thru:| [%DATE;P=popup.calendar(edateC);I=popup.calendar%.20edateC!edateC_*];
                  {endregion};
                  {line=1,0};
                  {region}
                  <15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
                  {endregion};
                  %dlg%,<<%code%
                  IF left(a_dlg_button,7) = "bdateC_" THEN
                      IF a_dlg_button = "bdateC_killfocus" THEN
                          IF bdateC = "" THEN
                              bdate = {}
                          ELSE
                              IF isdate(bdateC)
                                  bdate = ctod(bdateC)
                                  bdateC = dtoc(bdate)
                              ELSE
                                  msgbox("","Invalid Date!")
                                  bdatec=""
                                  ui_dlg_ctl_goto("Enter Dates","bdate")
                              END IF
                          END IF
                      END IF
                      a_dlg_button = ""
                  END IF
                  if left(a_dlg_button,7) = "edatec_" then 
                   if a_dlg_button = "edatec_killfocus" then 
                          IF edateC = "" THEN
                              edate = {}
                          ELSE
                              IF isdate(edateC)
                                  edate = ctod(edateC)
                                  edateC = dtoc(edate)
                              ELSE
                                  msgbox("","Invalid Date!")
                                  edatec=""
                                  ui_dlg_ctl_goto("Enter Dates","edate")
                              END IF
                          END IF
                   end if 
                   a_dlg_button = ""
                  end if 
                  %code%)
                  Cole Custom Programming - Terrell, Texas
                  972 524 8714
                  [email protected]

                  ____________________
                  "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                  Comment

                  Working...
                  X