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

onwrotefield field event logic error

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

  • onwrotefield field event logic error

    For the field Rx_no the user will routinely be entering a 7 digit or less number. The number is embedded in a string available in a bar code in characters 3 thru 9. To facilitate this I put the following code in the onwrotefield field rule event for the field Rx_no:

    Code:
    rx_no.text = substr(rx_no.text,3,7)
    This works fine, removing characters 1,2 and 10 and beyond from the bar code read string. I then thought that a person might occasionally want to enter the 7 digit number manually, so I changed my onwrotefield code to the following:

    Code:
    if(len(rx_no.text)>7,substr(rx_no.text,3,7),rx_no.text)
    This fails to strip any characters from the scanner submission, as does:

    Code:
    if(len(rx_no.text)>7,rx_no.text=substr(rx_no.text,3,7),rx_no.text)
    Or:

    Code:
    if(len(rx_no.text)>7,rx_no.text=substr(rx_no.text,3,7),rx_no.text=rx_no.text)
    What am I missing, or is there a better way?

    Bob Arbuthnot

  • #2
    Re: onwrotefield field event logic error

    I am not in a position to test at the moment but you may need to use iif() instead of if().

    From the Help

    Note : Use IIF() instead of IF() when using the expression in an Xbasic script.
    or

    Try using the 'a_field_value' system variable in the CanWriteField event
    Code:
    a_field_value.value = iif(len( a_field_value.value)>7,substr(a_field_value.value,3,7),a_field_value.value)
    or

    Code:
    If  len(a_field_value.value) > 7 Then
           a_field_value.value = substr(a_field_value.value,3,7)
    End If
    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: onwrotefield field event logic error

      trim it.

      The length of any field is the maximum length defined for that field - including all trailing blanks. (Remember, computers are stupid. To them, blank spaces are just another character.) The following should work:

      if(len(trim(rx_no.text))>7,substr(rx_no.text,3,7),rx_no.text)

      Comment


      • #4
        Re: onwrotefield field event logic error

        Originally posted by CALocklin View Post
        trim it.

        The length of any field is the maximum length defined for that field - including all trailing blanks. (Remember, computers are stupid. To them, blank spaces are just another character.) The following should work:

        if(len(trim(rx_no.text))>7,substr(rx_no.text,3,7),rx_no.text)
        Well, this is certainly confusing me. Since onwrotefield is a table level field rule event, is it wise to refer to a form object's text (rx_no.text) for validation or transformation? That may have no context if editing or entry is done outside the form.

        Should it be

        if(len(trim(rx_no))>7,substr(rx_no,3,7),rx_no)

        Ok, now I think I see it a little clearer. The script for the onwrotefield event (actually I would use the canwritefield event) could be

        Code:
        if len(alltrim(ref_no.text))>7
        	ref_no.text = substr(ref_no.text,3,7)
        end if
        or using Cal's line of attack

        Code:
        rx_no.text = if(len(trim(rx_no.text))>7,substr(rx_no.text,3,7),rx_no.text)
        Last edited by Stan Mathews; 05-21-2007, 11:14 AM.
        There can be only one.

        Comment


        • #5
          Re: onwrotefield field event logic error

          Stan, you are correct. I didn't pay attention to the fact that this was a field rule (table level) event rather than a form level event.

          While something like "ref_no.text" might work (maybe only because the form also happens to be open at the time and there is a "ref_no" object?), I certainly wouldn't recommend it.

          Instead, I'd use something like:
          tc = table.current() 'In

          Comment


          • #6
            Re: onwrotefield field event logic error

            Stan, you are correct. I didn't pay attention to which event was being used. Both the fact that this was a field rule (table level) event rather than a form level event and this was an "On" rather than a "Can" event are significant.

            While something like "ref_no.text" might work (maybe only because the form also happens to be open at the time and there is a "ref_no" object?), I certainly wouldn't recommend it.

            Instead, I'd use something like:
            tc = table.current()
            tc.rx_no = if(len(trim(tc.rx_no))>7,substr(tc.rx_no,3,7),tc.rx_no)

            And, I would use the CanWrite event as you suggested.

            NOTE: In the CanWrite and OnWrote events, table.current() will ALWAYS refer to the table currently being written to even if it is currently being used in a set. (The definition of "currently" is the issue here - when it is writing to a specific field, the system knows that the "current" table is the one being written to.)

            I would NOT use the "arrow" method such as MyTableName->rx_no because there is always the possibility that Alpha might be using an alias name and the name you've specified may be pointing to the wrong instance of the table. While this may not be a common situation, I have run into it.

            Edit: Hmmm, how did that first 1/2 message get sent?

            Comment


            • #7
              Re: onwrotefield field event logic error

              Correct me if I'm wrong on this, but I think you have to refer to a_field_value in a canwritefield event in field rules - otherwise you are referencing the actual field's value instead of what its a'fixin' to be - if it was "seven" before you got there and you typed "eight" the field's value is still "seven", but a_field_value is "eight".
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              martin_w_cole@msn.com

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment


              • #8
                Re: onwrotefield field event logic error

                This is not my best day. (My excuse is that I had to take my wife to 3 different doctors today and it really messed up my schedule - should never have answered anything on the board today.)

                Yes. In the CanWrite event you should be using A_field_value.value to refer to the new text in the current field.

                Tim's method using A_field_value - but adding the Trim() command - is probably best. (I got focused on the IIF vs. IF which really shouldn't matter.)
                Code:
                a_field_value.value = iif(len( TRIM(a_field_value.value))>7,substr(a_field_value.value,3,7),a_field_value.value)
                I think it was fixed recently but I've had problems in the past using A_field_value in the "middle" of an expression. If there is still a problem, you may still have to use a script in the field rule something like this:
                Code:
                result = A_field_value.value
                IF len(trim(result)) > 7
                  result = substr( result, 3, 7 )
                ELSE
                  result = result
                END IF
                A_field_value.value = result

                Comment


                • #9
                  Re: onwrotefield field event logic error

                  they fixed it - the same syntax as in 4.5 works
                  Cole Custom Programming - Terrell, Texas
                  972 524 8714
                  martin_w_cole@msn.com

                  ____________________
                  "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                  Comment


                  • #10
                    Re: onwrotefield field event logic error

                    Thank you Tim, Cal, Stan, and Martin,

                    The following works as needed:

                    Code:
                    rx_no.text = if(len(trim(rx_no.text))>7,substr(rx_no.text,3,7),rx_no.text)
                    If someone could please clarify for me, Cal and Stan you both expressed preference of canwritefield over onwrotefield. Since the form is modal does it really make any difference which is used?

                    From the Help Files:

                    CanWriteField
                    Before the cursor exits the field. Use to detect what the user has entered into the field before it has been saved.

                    OnWroteField
                    After the cursor exits the field.
                    Thank you again for your help.

                    BA

                    Comment


                    • #11
                      Re: onwrotefield field event logic error

                      I think the reason for using CanWrite is because you want to manipulate the data in the current field and also see the change when the cursor leaves the field. If instead you were gathering info for the next field, like setting a variable, then OnWrote would be good for that. I may be wrong here, but OnWrote might not show the change on screen until the record is saved.
                      Robin

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

                      Comment


                      • #12
                        Re: onwrotefield field event logic error

                        Hi Robin,

                        Thanks for trying to clear my fog. What I'm seeing, in this instance anyhow, is that the text is correctly manipulated upon leaving the rx_no field.

                        BA

                        Comment

                        Working...
                        X