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

Previous values + validation?

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

    Previous values + validation?

    Does anyone know if V5 will allow for something like a Previous Values lookup style with table validation of entries? In other words, as with previous values the user types just as much of the new entry as necessary to get to the right one AND he or she cannot put in a new one that is not in the validation table. As near as I can tell this is not possible with V4 and I have yet to see an indication that it will be possible in V5 (unless perhaps one builds all or part of it with Xbasic). If anyone knows of an easy way to do it with V4, please let me know. And yes, I know there are other perhaps even better ways to do almost the same thing but I have a prospective client who wants what I do to function exactly the way his current application handles the process of this particular input, and that includes not having to type all of a valid entry.

    Also, any new input on whether Alpha's way of dealing with previous values is reliable enough to use with fairly short fields (say 20 characters)? I worry about corrupt indexes and crashes.

    Ray Lyons


    #2
    RE: Previous values + validation?

    Hi Ray,

    I remember Selwyn demoing this. It was impressive.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: Previous values + validation?

      Here's what I found on trying a few things:

      If you select SIMPLE LIST in the LOOKUP field rule, and ALLOW ANY VALUE (I know that's not what you want, but I wanted to be thorough), the field will pick out the closest value as you enter characters. Let's say a valid value is THREE, and you enter the T and the H. In both cases, THREE is filled in, with the remaining REE highlighted. But if you then enter an I, the REE disappears, leaving only what you have entered.

      Now, if you set the condition to FORCE CLOSEST MATCH or POPUP ON MISMATCH (I would have bet that the latter would have worked - good thing I don't go to casinos!), and then type T, THREE appears and does NOT let you add any more characters.

      But here's something else that's interesting. If you had two valid entries starting with T (THREE and TRIDENT [hmm...am I hung up on triplets??]), and you press T once, THREE appears in the field. Press T again and then TRIDENT appears. So, this is getting closer to what you want.

      Of course, if you have a lot of entries for a given letter (THREE, TRIDENT, TRIPLET, TERTIARY, THIRD [how's that, folks??]), it could become a real pain to get the entry you want.

      Comment


        #4
        RE: Previous values + validation?

        Ray,

        You can put in a validation expression that uses the exist function in the field rule.

        It won't put in the initial values (which are pulled from the previous values in the current table), but will validate whether the enter valued is in the other table.

        Does this give you what you need?

        Regards,

        Ira J. Perlow
        Computer Systems Design & Associates
        [email protected]
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment


          #5
          RE: Previous values + validation?

          Thanks Bill, I'll play around with a number of your suggestions.

          Ray

          Comment


            #6
            RE: Previous values + validation?

            >>You can put in a validation expression that uses the exist function in the field rule.

            Comment

            Working...
            X