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

ISBLANK() trouble

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

  • ISBLANK() trouble

    Hi All,

    It seems ISBLANK() is working backwords from how I think it should be, I have put a validation rule in field rules that says ISBLANK(customer_name) then in the message "Customer Name" is required. What is happ is it shows the message if the customer_name field is NOT blank. If I make it .NOT.ISBLANK(customer_name) then it pops up the message when thiers no value. Y is this happing?
    Kind Regards,
    Ray Roosa
    Raylin Micro, LLC.

  • #2
    Re: ISBLANK() trouble

    should be:
    ISBLANK("customer_name")

    Comment


    • #3
      Re: ISBLANK() trouble

      Originally posted by G Gabriel View Post
      should be:
      ISBLANK("customer_name")
      Thank you for the reply however I did not exsplain in my exsample that I do have the quots around the customer name but the function seems to be working backwards, ISBLANK("customer_name") then fire my message but what is happing is it only fires my message when its not blank innless I use .NOT.ISBLANK("customer_name") then it fires my message when the field is blank, y is this happing? is it not working backwards?
      Kind Regards,
      Ray Roosa
      Raylin Micro, LLC.

      Comment


      • #4
        Re: ISBLANK() trouble

        Originally posted by Rayr View Post
        Thank you for the reply however I did not exsplain in my exsample that I do have the quots around the customer name but the function seems to be working backwards, ISBLANK("customer_name") then fire my message but what is happing is it only fires my message when its not blank innless I use .NOT.ISBLANK("customer_name") then it fires my message when the field is blank, y is this happing? is it not working backwards?
        For one thing you should be using ISNOTBLANK() rather than .NOT.ISBLANK(). Possibly for another, both functions return either a .T. or a .F., so maybe you need ISBLANK("customer_name")=.t. (or = .f. depending on what you are doing). See if that works as desired.

        Ray

        Comment


        • #5
          Re: ISBLANK() trouble

          Ray

          When using custom validation rules when the customer name is blank then the validation rule "isblank("customer_name") is true then the validation will allow the blank and the message will not be displayed. By the same token if the customer name has an entry then the validation rule "isnotblank("customer_name") is true and the record will save and the message will not be displayed.

          Here is a partial quote from the help file

          If all validation expressions evaluate to TRUE for the record, the entered value is allowed in the field. Otherwise, the entry is rejected, and a validation error message for the first expression to fail appears.
          I guess you could say that it is backward but when you think about it, what the validation rule is saying is I will allow it if the condition is true.

          I hope that explains it a little.

          Tom

          Comment


          • #6
            Re: ISBLANK() trouble

            First Ray:
            I have put a validation rule in field rules that says ISBLANK(customer_name)
            I think you got your wires mixed up. That should go in data entery not validation. Validation checks to see that the value entered is within acceptable parameters. You need to make data entery "required".

            Other Ray:
            Isblank("field")
            and
            Isblank("field")=.t.
            are the same.
            The default for logical functions is "true".

            Comment


            • #7
              Re: ISBLANK() trouble

              This has the look of a bug, but IT IS NOT.

              I am going to make a guess here:
              The field to which you made this field rule is the first field that receives focus. Right?

              Comment


              • #8
                Re: ISBLANK() trouble

                Originally posted by G Gabriel View Post
                This has the look of a bug, but IT IS NOT.

                I am going to make a guess here:
                The field to which you made this field rule is the first field that receives focus. Right?
                Yes it is the first field to get focus, does this mean something?
                Kind Regards,
                Ray Roosa
                Raylin Micro, LLC.

                Comment


                • #9
                  Re: ISBLANK() trouble

                  Originally posted by G Gabriel View Post
                  First Ray:

                  I think you got your wires mixed up. That should go in data entery not validation. Validation checks to see that the value entered is within acceptable parameters. You need to make data entery "required".

                  Other Ray:
                  Isblank("field")
                  and
                  Isblank("field")=.t.
                  are the same.
                  The default for logical functions is "true".
                  I had tryed using the data entry "required" before using validation rules the only trouble using data entry "required" is when the message pops up it uses the default field name CUSTOMER_NAME instead of the descriptive name, Company Name witch is much better looking. I dont know if Alpha Software can change this to use the descriptive name if it exist, then we would not have to reinvent the wheel since its already their.
                  Kind Regards,
                  Ray Roosa
                  Raylin Micro, LLC.

                  Comment


                  • #10
                    Re: ISBLANK() trouble

                    Originally posted by Raymond Lyons View Post
                    For one thing you should be using ISNOTBLANK() rather than .NOT.ISBLANK(). Possibly for another, both functions return either a .T. or a .F., so maybe you need ISBLANK("customer_name")=.t. (or = .f. depending on what you are doing). See if that works as desired.

                    Ray
                    Hi Ray,

                    ISNOTBLANK("Customer_name") worked perfectly. I would like to thank everyone for all their help with this. I have used alpha on and off since their DOS days but have not focused on it so I guess you can consider me new now, i wish I had stuck with it all these years but now I am ready to commit to Alpha Five, one of the best things about Alpha is this community of people helping each other. I look forward to being able to help out someone some day on here also. :)

                    </IMG>
                    Kind Regards,
                    Ray Roosa
                    Raylin Micro, LLC.

                    Comment

                    Working...
                    X