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

key_unique() I'm missing something

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

    key_unique() I'm missing something

    I must not be seeing something. In build 2055 I added the following code on the CanSaveRecord event of rules for the contact table.

    Code:
    if .not. key_unique("fullname")
    	cancel()
    	ui_msg_box("Required Unique Value","Combination of blah blah blah")
    end if
    This gives the attached error. if I change the code to
    if .not. key_unique("[email protected]")
    then I get "not an open index".

    fullname is a calculated field of all the names. The index works fine.

    Bill.

    #2
    Re: key_unique() I'm missing something

    Bill,

    The docs say that where you have fullname you should have the name of the index that you are testing the uniqueness of. The index itself will tell Alpha what fields it needs to look for. This function is for testing the uniqueness of the INDEX key not the uniqueness of a field. You would, therefore, need an index called fullname that includes all the fields you want tested.

    Comment


      #3
      Re: key_unique() I'm missing something

      Fullname is both the fieldname and the indexname.

      One thing that supprised me (besides the fact that it did not work), was that the error referred to Variable Name. It seems that an error for that function should refer to index tag.

      I mention that it is a calculated field because that means the normal custom validation rule can't be used for_unique().

      Bill.
      Last edited by Bill Parker; 03-10-2009, 06:31 PM.

      Comment


        #4
        Re: key_unique() I'm missing something

        Possible fix, possible bug. I put key_unique() in the custom validations on a different field and it works fine. so something about CanSaveRecord event that prevents it from working.

        Also, in the custom validation expression builder I get parameter help to select the tag name. In CanSaveRecord parameter help is not avaliable.

        Someone may know why this is, otherwise I will submit a bug report.

        Bill.

        Comment


          #5
          Re: key_unique() I'm missing something

          Bill,
          Did you ever submit a bug report? I'm using v10 and getting the same errors you reported here.
          Ernie

          Comment


            #6
            Re: key_unique() I'm missing something

            Alpha was not fixing anything in v9 at that point.

            Here is the code I currently use on CanSaveRecord.
            Code:
            t = table.current()
            ...
            'changed value is not saved if check is done on t.  must do check on t2.
            Dim vCount as N
            t2 = table.open("contact")
            i = t2.query_create("N","Fullname=" +quote(t.fullname) +".and.recno()<>" +t.recno())
            vCount = i.records_get()
            t2.close()
            
            if vCount > 0
            'if .not. key_unique("Lastname_Company")	'get "variable Fullname not found". can't use t. above, must open t2. probably a bug.
            	vReply = p_msg_box("Warning - Duplicate Fullname","Fullname = " +quote(alltrim(t.FULLNAME)) -" already exists.  Create record with duplicate name?" +crlf(2) +"Or cancel this record and find existing record.","Cancel,Create Duplicate Name","attention")
            	if vReply = "Create Duplicate Name"
            		'allow record to be saved
            	else
            		cancel()
            '		ui_msg_box("Notice","Cancel data entry, then look for existing record.",UI_INFORMATION_SYMBOL)	'too much
            	end if
            end if
            Actually, thanks for asking. I see that the code still allows the user to accept a duplicate which I need to change!

            Bill.

            Comment


              #7
              Re: key_unique() I'm missing something

              Thanks, Bill. Must still be a bug. Will post in v10 forum and see if anyone responds there. If not, will submit.
              Ernie

              Comment


                #8
                Re: key_unique() I'm missing something

                It's a bug (I say that tongue in cheek as alpha might not have intended for it to work this way, full explanation will follow if interested) but it's very easy to get around.
                Here is what your code should look like:
                Assuming you have a field, that is set as calculated and is set to concatenate the Fname & Lname and is called "FullName"
                Assuming you have an index based on this field and the index is called: "Full_Name"
                Here is the code in the CanSave event of the Field Rules:
                Code:
                dim global fullname as c
                fullname=your_table_name->fullname
                if .not.key_unique("full_name")
                	ui_dlg_box("Unique Value",<<%dlg%
                	{xmargin=2}
                	{ymargin=2}
                	This value is not unique;{lf};
                	<save><discard>
                	%dlg%,<<%code%
                	if a_dlg_button="discard"
                		cancel()
                	end if
                	%code%)
                end if

                Comment


                  #9
                  Re: key_unique() I'm missing something

                  G.,
                  My table is indexed on the combo of two fields in the table, an ID field (numeric)+datefield. I call it Date_Off. It's a combo of staff_id and Date_Off. Either using key_unique or key_exist both return the error that the "variable" Date_Off is not found.
                  I don't use a calculated field for this combo. Should I dim two globals and assign them to the values of these fields in the table?
                  Ernie

                  Comment


                    #10
                    Re: key_unique() I'm missing something

                    Originally posted by enstorms View Post
                    I don't use a calculated field for this combo. Should I dim two globals and assign them to the values of these fields in the table?
                    Ernie
                    That will work.

                    Comment


                      #11
                      Re: key_unique() I'm missing something

                      Found why my code was not working. Went back and re-read the help on validating duplicate entries in Field Rules.
                      In the record event CanSaveRecord:
                      Code:
                      dim tbl as p
                      tbl = table.current()
                      
                      if key_exist("Date_Off",STR([COLOR="red"]tbl.[/COLOR]STAFF_ID)+[COLOR="Red"]tbl.[/COLOR]DATE_OFF) .and. tbl.mode_get() = 2 then
                          cancel()
                      end if
                      I hadn't seen the tbl. in referencing the field of the key_exist() function.
                      Ernie

                      Comment


                        #12
                        Re: key_unique() I'm missing something

                        Good catch Ernie.

                        It is not so much the usage of the tbl pointer in the key.exist() function as it is where you are using the function. On a form based on a table you can usually refer to the field without it because the form has opened the table. In a script, not so easy.
                        There can be only one.

                        Comment


                          #13
                          Re: key_unique() I'm missing something

                          Stan,
                          Had a hard time trying to understand why it couldn't recognize the fieldname when it is in the field rules that it is taking place. Oh well, whatever works.
                          Ernie

                          Comment


                            #14
                            Re: key_unique() I'm missing something

                            In the field rules, yes, but it is code for an event for the field rules where different constraints apply. Easy to see why one would expect the event to know how interpret the field name.

                            Live and learn, eh? Glad you got it worked out. That's the best lwarning experience when you find it on your own.
                            There can be only one.

                            Comment

                            Working...
                            X