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

Point me in direction of specific help please...

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

    Point me in direction of specific help please...

    Can someone please tell me where to find Alpha help on field rules 'Validations'
    In particular I would like to ensure that certain records are unique, i.e. fields A+B+C qualify a record as unique.
    So I figure the "Value of expression must be unique" option is the one I need.
    I tried various combinations of combining these 3 fields but just got errors or the uniqueness rule wasn't applied.
    I have looked at the help for this but when I try to click on the relevant URL in both the help system and the wiki
    it either fails to display anything or in the case of the wiki reports a missing page.

    Paul

    #2
    Re: Point me in direction of specific help please...

    I tried various combinations of combining these 3 fields but just got errors or the uniqueness rule wasn't applied.
    Why not attach a sample table so we can diagnose your validation issues.

    Possibly the documentation doesn't point out boldly enough.

    For each of the multiple fields:

    Select "Value of expression must be unique" in the Uniqueness test list.

    In the Unique expression field enter an expression that evaluates to a character value and that includes all of the multiple fields that you want to test.
    There can be only one.

    Comment


      #3
      Re: Point me in direction of specific help please...

      Here you go - There should only be one of last two records...
      Attached Files

      Comment


        #4
        Re: Point me in direction of specific help please...

        Originally posted by Stan Mathews View Post
        Why not attach a sample table so we can diagnose your validation issues.

        Possibly the documentation doesn't point out boldly enough.
        The help you quote in your reply - where is it? I can't find it...
        Still not sure what it means, what is the exact structure of the expression?
        Paul

        Comment


          #5
          Re: Point me in direction of specific help please...

          The inline documentation. An example is given there.


          validation.png
          There can be only one.

          Comment


            #6
            Re: Point me in direction of specific help please...

            Still no wiser...
            Attached Files

            Comment


              #7
              Re: Point me in direction of specific help please...

              That probably should say

              Click Build Indexes and then Field Rules.

              Both toolbar buttons in the Index Definiton genie.
              There can be only one.

              Comment


                #8
                Re: Point me in direction of specific help please...

                That probably should say

                Click Build Indexes and then Field Rules.

                Both toolbar buttons in the Index Definiton genie.

                I am sorry but I cannot see what you the Alpha help is referring to. As far as I am concerned the files I attached earlier are correctly defined in line with what I can glean from the help for this topic but it does not seem to want to implement the uniqueness rule.
                Have I missed something, I am a bit confused that this uniqueness test is only available to specify against one field. Should I replicate it for the other two fields as well?
                So confused...
                Paul

                Comment


                  #9
                  Re: Point me in direction of specific help please...

                  There are two methods in that section of the documentation.

                  One headed Testing each field: and the other Testing the combined value:

                  Which are you trying to implement (I don't think you can use both at the same time)?

                  My attachment indicates 1 2

                  the two buttons indicated in the docs (Click Build Indexes and then Field Rules).

                  validation.png
                  Last edited by Stan Mathews; 12-17-2012, 06:07 PM.
                  There can be only one.

                  Comment


                    #10
                    Re: Point me in direction of specific help please...

                    OK Stan, where I was getting confused was that Alpha did not complain about (or remove) the existing duplicate record, either when I rebuilt the indexes and/or recalculated the field rules.
                    As soon as I deleted it manually and used the default form to try and enter I got the error message.
                    The next programming issue I foresee is how I intend to populate this table, i.e. via a batch routine (script) and not by form entry.
                    For example, A and B is a total record whereas A,B and C is a sub-total record, so I assume that programmatically I will have to test for AB first, if it does not exist use a create record function if it does exist use an update record function and then follow the same logic for AB and C.
                    In which case maybe I don't need the uniqueness test in the first place as I will be controlling the records created and updated in the script...

                    Thanks for your help,

                    Paul
                    Last edited by pulsoft; 12-18-2012, 04:38 AM. Reason: big fat finger stubs

                    Comment

                    Working...
                    X