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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Validation Xbasic

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    Validation Xbasic

    Trying to do (what should be) a relatively simple conditional validation on a text box control (in a dialog component) using Xbasic. I'm sure I'm missing something very basic, but here it is:


    if e.data._TEXT1 = "Yes" then
    validate_TEXT2.hasError = .t.
    validate_TEXT2.errorText = "TEXT2 requires completion if TEXT 1 is yes."
    end if
    end function
    Tags: None
    #2
    Re: Validation Xbasic

    Debug(1)?
    Alpha Anywhere latest pre-release

    Comment

      #3
      Re: Validation Xbasic

      based on your error message, wouldn't you need:

      if e.data._TEXT1 = "Yes" and. e.data._TEXT2 = "" then
      validate_TEXT2.hasError = .t.
      validate_TEXT2.errorText = "TEXT2 requires completion if TEXT 1 is yes."
      end if

      Comment

        #4
        Re: Validation Xbasic

        Thanks Sarah and Chris. Chris, this worked! Much appreciated.

        Comment

          #5
          Re: Validation Xbasic

          if e.data.Disposed=True and. e.data.DisposDate = "" then
          validate_DisposDate.hasError = .t.
          validate_DisposDate.errorText = "DisposDate cannot be blank."
          end if


          e.data.Disposed is a check box, if it is checked, then it is true, if unchecked, it is false.


          This code does not work, I also tried to add quotation marks around TURE, but it does not work. Please help me!

          Comment

            #6
            Re: Validation Xbasic

            e.data.Disposed is a character type
            Logical values are apples.
            Character types are oranges.
            Can we compare?

            You must convert the character to a logical value in order to compare, this is the best option and you SHOULD use it:
            if convert_type(e.data.Disposed,"L")==.t. and. e.data.DisposDate== "" then
            validate_DisposDate.hasError = .t.
            validate_DisposDate.errorText = "DisposDate cannot be blank."
            end if

            Here is another option - and I also illustrate how comparisons work etc
            if e.data.Disposed=="True"
            'Comparing to character This probably didnt work because maybe e.data.Disposed is "t" or "T" or "true" (lowercase). You can do a case insensitve search like this
            'if upper(e.data.Disposed)=="TRUE"
            You can put this code in for debuggin:
            validate_DisposDate.hasError = .t.
            validate_DisposDate.errorText = "Value in e.data.disposed: "+e.data.Disposed+" Type:"+typeof(e.data.disposed)

            You will see that the type returns "C" meaning character

            .t. and .f. are of type "L" - Logical

            So, if you compare a character to a logical, you're gonna have a bad time.
            Scott Moniz - Computer Programmer/Analyst
            REA Inc.
            http://reainc.net
            (416)-533-3777
            [email protected]

            REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
            If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
            contact us to discuss options.

            Comment

              #7
              Re: Validation Xbasic

              Originally posted by aburningflame View Post
              e.data.Disposed is a character type
              Logical values are apples.
              Character types are oranges.
              Can we compare?

              You must convert the character to a logical value in order to compare, this is the best option and you SHOULD use it:
              if convert_type(e.data.Disposed,"L")==.t. and. e.data.DisposDate== "" then
              validate_DisposDate.hasError = .t.
              validate_DisposDate.errorText = "DisposDate cannot be blank."
              end if

              Here is another option - and I also illustrate how comparisons work etc
              if e.data.Disposed=="True"
              'Comparing to character This probably didnt work because maybe e.data.Disposed is "t" or "T" or "true" (lowercase). You can do a case insensitve search like this
              'if upper(e.data.Disposed)=="TRUE"
              You can put this code in for debuggin:
              validate_DisposDate.hasError = .t.
              validate_DisposDate.errorText = "Value in e.data.disposed: "+e.data.Disposed+" Type:"+typeof(e.data.disposed)

              You will see that the type returns "C" meaning character

              .t. and .f. are of type "L" - Logical

              So, if you compare a character to a logical, you're gonna have a bad time.

              I just tried, it gives me error message, "extra characters at end of expression Error Line 3 Column 1"

              But it is just "if" at that place, nothing special.

              Here is my code, also I tried "==" and "=" both.

              function validate_DisposalAcctNo as p (e as p)

              if convert_type(e.data.Disposed,"L")=.t. and. e.data.DisposalAcctNo = "" then
              validate_DisposalAcctNo.hasError = .t.
              validate_DisposalAcctNo.errorText = "DisposalAcctNo cannot be blank."
              end if


              end function

              Comment

                #8
                Re: Validation Xbasic

                I use window alert to display "Disposed" value, if it is checked, the alert window displays the word "true". no quotation mark. unchecked, display "false". All in lower case.

                Comment

                  #9
                  Re: Validation Xbasic

                  Hi, I just put these codes in without giving me any error message. replace t with true。 However, in preview, if i leave that field in blank, it does not give me any warning info, and can be saved as empty....

                  function validate_DisposalAcctNo as p (e as p)

                  if convert_type(e.data.Disposed,"L")==.true. and. e.data.DisposDate== "" then
                  validate_DisposDate.hasError = .t.
                  validate_DisposDate.errorText = "DisposDate cannot be blank."
                  end if


                  end function

                  Comment

                    #10
                    Re: Validation Xbasic

                    if convert_type(e.data.Disposed,"L")==.true. and. e.data.DisposDate== "" then
                    validate_DisposDate.hasError = .t.
                    validate_DisposDate.errorText = "DisposDate cannot be blank."
                    end if

                    How did you use alert to display the disposed value? - You dont need to do that.
                    Try this:
                    function validate_DisposalAcctNo as p (e as p)
                    'debugging
                    validate_DisposDate.hasError = .t.
                    validate_DisposDate.errorText = "DIsposed: "+e.data.Disposed+" Type: "+typeof(e.data.Disposed)
                    end 'kill this script early so code below doesnt execute

                    if convert_type(e.data.Disposed,"L")==.t. and. e.data.DisposDate== "" then
                    validate_DisposDate.hasError = .t.
                    validate_DisposDate.errorText = "DisposDate cannot be blank."
                    end if
                    end function

                    Run your grid, click the disposed checkbox and click Submit - Tell me what the above says
                    You are going to see something liek DIsposed: 0 Type: L
                    or Disposed: True Type: C or something.



                    In your e.data.Disposed checkbox properties is the 'Treat field as Logical Field?' checked?
                    Is your checkbox Initial Value set to 0? (False)
                    The following is 110% correct as far as I can see.

                    Code:
                    function validate_DisposalAcctNo as p (e as p)
     if convert_type(e.data.Disposed,"L")==.t. and. e.data.DisposDate== "" then
         validate_DisposDate.hasError = .t.
        validate_DisposDate.errorText = "DisposDate cannot be blank."
     end if
end function
                    Last edited by aburningflame; 09-06-2013, 05:04 PM.
                    Scott Moniz - Computer Programmer/Analyst
                    REA Inc.
                    http://reainc.net
                    (416)-533-3777
                    [email protected]

                    REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
                    If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
                    contact us to discuss options.

                    Comment

                      #11
                      Re: Validation Xbasic

                      The logical 'and' is missing a leading period.
                      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

                        #12
                        Re: Validation Xbasic

                        1.jpg

                        please check the attached picture. it really does not work. gives me error message. Thank you!

                        Comment

                          #13
                          Re: Validation Xbasic

                          i attached pic above. Please help me! Thank you!

                          Comment

                            #14
                            Re: Validation Xbasic

                            As Tim said you need to use:

                            .and.
                            Peter
                            AlphaBase Solutions, LLC

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

                            Comment

                              #15
                              Re: Validation Xbasic

                              Originally posted by Peter.Greulich View Post
                              As Tim said you need to use:

                              .and.
                              function validate_DisposalAcctNo as p (e as p)
                              'debugging
                              validate_DisposDate.hasError = .t.
                              validate_DisposDate.errorText = "DIsposed: "+e.data.Disposed+" Type: "+typeof(e.data.Disposed)
                              end 'kill this script early so code below doesnt execute

                              if convert_type(e.data.Disposed,"L")==.t. and. e.data.DisposDate== "" then
                              validate_DisposDate.hasError = .t.
                              validate_DisposDate.errorText = "DisposDate cannot be blank."
                              end if
                              end function

                              Run your grid, click the disposed checkbox and click Submit - Tell me what the above says
                              You are going to see something liek DIsposed: 0 Type: L
                              or Disposed: True Type: C or something.


                              I tried this..but just simply allows me submit it, it didn't give me any info.

                              Comment

                              Previous 1 2 template Next
                              Working...
                              X