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

validation field rule

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

    validation field rule

    I have two numeric fields in the same table. They are part of an embedded browse on a salesform attached to a set. I do not want the user to be able to enter a value in one field when the other already has a value, and visa-versa. I think I can probably (easily) do this under "validations" in the field rules, but haven't had any luck with the right combination of definitions yet.

    The two fields are: "qty1" and "csqty1", both in treatments.dbf. I've tried this validation field rule for the "qty1" field:
    cross file validation:simple
    test:must not exist in
    table:treatments.dbf
    field:csqty1

    I also tried:
    cross file validation:none
    custom validations table -validation: csqty1=0
    message: "you have already entered a csqty"

    When I test these two rules, I plug in a value for csqty1, then I get an error message when I leave the embedded browse. Any suggestions? Thanks.

    #2
    RE: validation field rule

    Becky,

    This is a little clumsy in practice but give it a try. Go to the events tab for qty1 and edit it's canwritefield event to be (substitute your actual table name for "yourtable")

    ''XBasic
    if isnotblank("yourtable->csqty1")
    ui_msg_box("Sorry","Already entered csqty1")
    cancel()
    end if

    and do the same for csqty1

    ''XBasic
    if isnotblank("yourtable->qty1")
    ui_msg_box("Sorry","Already entered qty1")
    cancel()
    end if
    There can be only one.

    Comment


      #3
      RE: validation field rule

      Leave it to me to find the hard way.

      Forget the prior post. Just edit the data entry tab in the field rules, skip condition, for each field

      for qty1 skip condition is isnotblank("csqty1")

      for csqty1 skip condition is isnotblank("qty1")
      There can be only one.

      Comment


        #4
        RE: validation field rule

        Thanks, Stan. That sounds simple. I also tend to look for the hardest ways to do things.

        Comment


          #5
          RE: validation field rule

          Let me add something to Stan's method:

          for qty1 skip condition is:
          isnotblank( "csqty1" ) .and. isblank( "qty1" )

          This allows you to get into the qty1 field to delete it in the case that something is in both fields. OK, this shouldn't happen but, based on experience, it does. Either existing data is already bad or the field rules get changed temporarily or bad data gets imported or a global update is wrong or ... who knows?

          Comment


            #6
            RE: validation field rule

            Cool addition and one I didn't consider. I'll file that away for future use, too.
            There can be only one.

            Comment

            Working...
            X