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

Strange character causing an error in memo field

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

  • Strange character causing an error in memo field

    I have a button on a form that adds a note to a memo field on the form using the following code:

    Code:
    DIM SHARED NotesVar as C
    DIM SHARED DialBox as C
    ok_button_label = "&OK"
    cancel_button_label = "&Cancel"
    DialBox = ui_dlg_box("Enter Notes",<<%dlg%
    {region}
    Notes:| [%mw%.40,5NotesVar];
    {endregion};
    {line=1,0};
    {region}
    <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};
    %dlg%)
    
    If Var->NotesVar=""
    	end 
    	ELSE
    
    Dim P as P
    DIM SHARED Test AS C
    
    vMode = parentform.mode_get()
    
    IF vMode = "CHANGE" .or. vMode = "ENTER"
    	parentform.commit()
    END IF
    
    tbl = table.current() 
    p.text=tbl.Notes
    
    tbl.change_begin()
    If alltrim(tbl.Notes) = ""
    	tbl.Notes = tbl.Notes + date_format(date(),"MM-dd-yy") +" (" + word(api_getusername(),1) +"): " + var->NotesVar
    	ELSE
    	tbl.Notes = tbl.Notes + crlf() +date_format(date(),"MM-dd-yy") +" (" + word(api_getusername(),1) +"): " + var->NotesVar
    	END IF
    tbl.change_end(.t.)
    Notes.refresh()
    topparent.commit()
    
    tc = table.current()
    tc.change_begin()
    tc.change_dtf = now()
    tc.change_by = api_getusername()
    tc.change_end(.t.)
    change_dtf.refresh()
    NotesVar = ""
    END IF
    We started receiving an error when attempting to add a note to one specific error and could not figure out why. It was generating an error stating incorrect data type pointing to the line above - If alltrim(tbl.Notes) = ""

    When viewing the memo field on the form, it appears fine, however if I view the table from the control panel, find that record and inspect the notes field, I see an odd character. I've attached a picture of this character.

    I have no idea what this character is, how it got there, how to prevent it from showing up again, or how to make my code above ignore it.

    If I delete the character while viewing the table from the control panel, we quit receiving the error when running script.

    Any suggestions?

    char.jpg

  • #2
    Re: Strange character causing an error in memo field

    Assuming this is a memo field, and not an RTF memo field...

    Was the text of the note "pasted" into the memo field variable from another source?

    Memo fields are limited to text. Somehow someone is trying to include non-printable control codes. No can do.

    Comment


    • #3
      Re: Strange character causing an error in memo field

      Originally posted by Tom Cone Jr View Post
      Assuming this is a memo field, and not an RTF memo field...

      Was the text of the note "pasted" into the memo field variable from another source?

      Memo fields are limited to text. Somehow someone is trying to include non-printable control codes. No can do.
      Tom,

      It's definitely a memo field, not an RTF field.

      Also, the text of the note was manually typed in and not copied from another source.

      I suspect that character was generated as a result of a 'fat finger' combo accidentally pressed while the user was entering the text.

      Is there a way to prevent 'non standard' characters to be saved in the first place?

      Thanks

      Comment


      • #4
        Re: Strange character causing an error in memo field

        Tim,

        Stan M, has reminded me that my suggestion could lead to big trouble. Sorry!

        Remspecial will remove your punctuation.

        So, its not a good choice for you here.

        Sorry.

        I recall wrestling with this a long time ago and wound up writing code that loops through each character in the memo field and if the ascii value of the current character was below or above the desired alphanumeric range my script converted the "character" to a blank space.

        --tom
        Last edited by Tom Cone Jr; 03-25-2013, 11:37 AM.

        Comment


        • #5
          Re: Strange character causing an error in memo field

          Looks a bit like an ASCII character out of the Alternate Char set.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          There are 3 things you can do in any situation;
          Live with it, Change it or Walk away from it.

          Comment


          • #6
            Re: Strange character causing an error in memo field

            I appreciate the responses.

            I found that character in the ascii table and it is generated by pressing alt + 11 on the keypad.

            Perhaps I should look into disabling the alt key when entering text?

            Tim

            Comment


            • #7
              Re: Strange character causing an error in memo field

              See, us old timers do know stuff (if we don't forget it, that is).
              Alt+Keypad as you found out is a quick way of getting ASCII characters into a text field.
              Problem comes with using Alt+171 to get . It's easier than looking for symbols and I use it a lot.
              Not sure how you could get around this, but disabling the Alt key is s good start.
              See our Hybrid Option here;
              https://hybridapps.example-software.com/


              There are 3 things you can do in any situation;
              Live with it, Change it or Walk away from it.

              Comment


              • #8
                Re: Strange character causing an error in memo field

                Tim, if I were you, I'd be curious whether this was accidental or deliberate. Fat fingers wouldn't do this. -- tom

                Comment


                • #9
                  Re: Strange character causing an error in memo field

                  We call it Sausage fingers over here.
                  Depends where the Alt key is located.
                  ♂, no , no (_|_) Yes!
                  See our Hybrid Option here;
                  https://hybridapps.example-software.com/


                  There are 3 things you can do in any situation;
                  Live with it, Change it or Walk away from it.

                  Comment


                  • #10
                    Re: Strange character causing an error in memo field

                    Thought I'd pass along a follow up to this problem and how we solved it.

                    It turns out that the character was not being generated by an 'Alt 11' keystroke combination after all.

                    When I looked at it more closely, the character being generated was similar to the ascii character created by Alt-11 but not quite the same.

                    Today at the office, we found several records that had this problem and narrowed it down to records entered by one user. It turns out that when he was entering new records and entered text into a memo field, he occasionally used the 'Shift+Enter' combination when starting a new line of text.

                    Each time you press 'Shift+Enter' in a memo field, it generates this character which later causes the above error.

                    I prevented this key combination in the onkey event of the form and problem solved.

                    I appreciate the help!

                    Tim

                    Comment

                    Working...
                    X