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

New to Alpha FIve, some dubs

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

    New to Alpha FIve, some dubs

    Hi,

    I'm trying the trial version of A5 and I have come dubs, I read the docs and I'm still stoped:


    1. I'm trying to set a custom validation Field Rule, in the FIRSTNAME field in the AlphaSports sample, so I set the condition and after that I go to the default form of the customer table and the field rule is evaluated only when I try to save the record. According to the help the valid condition should be evaluated after exiting th fields and when the form is saved. I find also that the valid condition is not evaluated when editing a record, �Is there something I0m missing here?

    2. When I edit some record in the Customer Information form in the AlphaSports sample, if I clear some field, after exiting the field the previous field content is restored so I can not clear the field, in the other hand, if Ijust modify the field content, the new content of this field is saved ok.

    Thanks in advance,

    Rod.

    #2
    Re: New to Alpha FIve, some dubs

    Hi Rod,

    Seems like you are making good progress with your learning of Alpha.

    It is best if you only ask one question in each thread, this helps maintain the integrity of the question, answers and if any, conclusion.

    Q1, What is the custom validation Field Rule in the FIRSTNAME field you are trying to evaluate?

    Q2, I dont understand your question, which field/s are you talking about?
    Last edited by Keith Hubert; 05-18-2009, 02:41 AM.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: New to Alpha FIve, some dubs

      Question 2--works on version 8 no problem....I will test on v 9 tomorrow if noone else has. Unless you are only talking about the linkage ID number and that is something that you cannot clear or change...nor would you want to. Please be much more specific in your question(s).
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #4
        Re: New to Alpha FIve, some dubs

        Hi,

        Keit, MikeC, thanks for your prompt response. I see now that I was not clear in my previous message, so I'll try to explain deeper Q1.

        For this test I'm using the Customer table in the AlphaSports application.

        I'm trying to set a custom validation so I go tho the "Edit field rule.." right clicking over the customer table. In the dialog I go to the "Validations" tab and, in that tab, in the lower section "Custom validations".

        Here I'm trying to enter an expression to show a message if while editing or creating a new record the FIRSTNAME field is empty. The expression entered in the "Validation" column is "isblank(FIRSTNAME)", but this shows the message if the field is not empty, so I changed to "isnotblank(FIRSTNAME)", but the message never shows up, even when I left the field blank. So I want to know the way to go in this issue.

        Thanks again for your kind help.

        Regards,


        Rod.




        I know there is a specific option for this en the "Data ENtry" tab in the same dialog, for I'm trying to show my own message.




        Hope this is more clear than my previous try, Thanks for your help.



        rule (In the VALIDATION tab) so I can show a message if the field FIRSTNAME is left empty by the user. I know that I could use but I want to show my own message.

        Comment


          #5
          Re: New to Alpha FIve, some dubs

          Hi Rod,
          First off, make sure you have your syntax correct in the function you are using...isblank(FIRSTNAME) should have double-quotes around the fieldname like isblank("FIRSTNAME").

          Regarding field rules and messages. Field Rules will always bring up an Alpha Five message--no way to turn it off (in most cases). So if you also have a message come up, the user/you will have 2 messages each time it is triggered. Unless you also have purchased Alpha's Branding tool which allows you to customize the inherent Alpha message.

          Most will just skip the field rules and roll their own when your own message is wanted.
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


            #6
            Re: New to Alpha FIve, some dubs

            I tried these things and was able to get them to work as expected. Using:
            Code:
            expression: fieldname<>"Validate"    Message:"The field value cannot be 'validate'"
            When validate was the field value, the message fired when the record was saved.

            When the expression was fieldname<>"", then when the field was blank the message fired. And when a value was placed in the field and the record saved, it could be changed but not erased to a blank condition because the validation for denial of that condition was in place.

            To roll your own, like MikeC said, would be something like placing code on the form's field OnDepart event.
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment

            Working...
            X