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

Uniqueness Test

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

  • Uniqueness Test

    I am developing a scheduler for my database which contains the following fields (Among others):

    Appt_Date
    Appt_Start_Time
    Category

    Appt_Date = Date Field
    Appt_Start_Time = ShortTime Field
    Category = Text field that contains the type of appt it is (ie. Photoshoot, Sales Session, etc.)

    I also have a calculated field called Short_Appt2 that combines Appt_Date and Appt_Start_Time into one field that looks like: 04/16/2011 @ 11:00am

    I want the database to check as soon as the calculated field is populated, for uniqueness. That way I cannot double book an appointment within the same Category.

    I can have appointments on the same date and time as long as they are in DIFFERENT categories.

    Hope I was clear with all this.

    Thank you so much (in advance for any advice).

  • #2
    Re: Uniqueness Test

    Checkout the validation tab in field rules. And this page in the help
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    Comment


    • #3
      Re: Uniqueness Test

      The uniqueness function does not seem to work with time or calc fields.

      I created an index call Full_Appt with this expression:

      ALLTRIM(CATEGORY)+" on "+(APPT_DATE)+" @ "+(APPT_START_TIME) - which results with, for example, Photoshoot on 04/16/2011 @ 7:00pm

      Here is the code I used in RecordEvents:

      CanSaveRecord

      tbl = table.current()
      if key_exist("Full_Appt", ALLTRIM(CATEGORY)+" on "+(Appt_Date)+" @ "+(Appt_Start_Time)) then
      cancel()
      ui_msg_box("Error", "The Appt Time is already taken")
      end if

      I get the following error:

      Variable "Appt_Start_Time" not found.

      Any Ideas??
      Last edited by pcman_chris; 04-17-2011, 01:00 AM.

      Comment


      • #4
        Re: Uniqueness Test

        As per the help page the field names in the record event code need to be qualified with the table pointer.
        uses the same expression as the index as its second argument, with the exception that each field name is prefaced by " tbl. ".
        Code:
        tbl = table.current()
        if key_exist("Full_Appt", ALLTRIM(tbl.CATEGORY)+" on "+(tbl.Appt_Date)+" @ "+(tbl.Appt_Start_Time)) then
        cancel()
        ui_msg_box("Error", "The Appt Time is already taken")
        end if
        As an aside: Alpha starts evaluating expressions from the right to the left. That is why the error message referred to Appt_Start_Time and not CATEGORY. This can be confusing because one may think 'well the first two fields worked, what is wrong with the last one.'
        Tim Kiebert
        Eagle Creek Citrus
        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

        Comment


        • #5
          Re: Uniqueness Test

          You may want to proceed with care with this because my memory is that key_exist() is a problem when you modify some other field of a record as the record key then does already exist! But do not despair as there are other ways to tackle this problem.

          Comment


          • #6
            Re: Uniqueness Test

            Thanks so much! It still gets an error:

            Property not found, tbl.Appt_Start_Time Subelement not found

            BUT it seems to work! It will not let me save if the same time slot is already filled.

            Comment


            • #7
              Re: Uniqueness Test

              Gary, How else could I do this?

              Comment


              • #8
                Re: Uniqueness Test

                Originally posted by Garry Flanigan View Post
                You may want to proceed with care with this because my memory is that key_exist() is a problem when you modify some other field of a record as the record key then does already exist! But do not despair as there are other ways to tackle this problem.
                You are right. It works well when creating the record, but If I need to change/update that same record I get the pop-up!! Man that sucks.

                Comment


                • #9
                  Re: Uniqueness Test

                  Another illustration that to our dismay Alpha will do what we tell it to do, instead of what we want it to do.

                  Have you check the help file documentation on the function you're using (Key_exist) ?

                  Comment


                  • #10
                    Re: Uniqueness Test

                    Hi Tim,
                    That's interesting - I have never been able to get a pointer to work defined that way in field rule events. I thought it was necessary to use this format:

                    tablename->fieldname.

                    I'm going to try it...

                    Originally posted by Tim Kiebert View Post
                    As per the help page the field names in the record event code need to be qualified with the table pointer.
                    Code:
                    tbl = table.current()
                    if key_exist("Full_Appt", ALLTRIM(tbl.CATEGORY)+" on "+(tbl.Appt_Date)+" @ "+(tbl.Appt_Start_Time)) then
                    cancel()
                    ui_msg_box("Error", "The Appt Time is already taken")
                    end if
                    As an aside: Alpha starts evaluating expressions from the right to the left. That is why the error message referred to Appt_Start_Time and not CATEGORY. This can be confusing because one may think 'well the first two fields worked, what is wrong with the last one.'
                    Robin

                    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                    Comment

                    Working...
                    X