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

text parsing in a field

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

    #31
    RE: text parsing in a field

    Hi,

    There is also a particular case when there is no space at the beginning of email and the semicolon is concatened with the email like in the foll example

    E-MAIL:[email protected]

    so the whole phrase is parsed like an email address.

    Is there any possibility to consider the semicolon the left boundary of the email?

    regards,
    Corneliu

    Comment


      #32
      RE: text parsing in a field

      Hi Stan,

      Is there any possibility to add a check box on the form, when checked to disable the "on_change" event of the field?

      I mean that there are some cases when I want to disable the parsing facility of the field.

      Regards,
      Corneliu

      Comment


        #33
        RE: text parsing in a field

        Corneliu,

        As for the emails, it now picks up the appropriate substring (not always the last one). That was accomplished using filter_string() as mentioned above. Likewise, it now accounts for when substrings are preceded by a colon rather than a space. I simply used a strtran() within a *for_each() to place a space after every colon.

        As for the web addresses, however, they still pick the last space-delimited word on the line. Since I would have to pick the word which contains "hppt:", "www:" or ".net" it gets rather complicated again. Maybe you can make do and do manual changes for web addresses that are not on the end of a line.

        Steve

        Comment


          #34
          RE: text parsing in a field

          Hi Steve,
          Thanks a lot for the new version.
          generaly it works correctly but however I encountered some strange situations like follows

          -----

          ZEINEB B.Y F / MOB: 216 98 370 777
          E.Mail : [email protected]
          E.Mail: [email protected]
          please visit : www.mmuagroup.net

          -----

          where an email address is parsed as www2

          -----

          Sale & Purchase : [email protected]

          -----

          is parsed both as an email and an web address

          Maybe you can figure out what happens

          Regards,
          Corneliu

          Comment


            #35
            RE: text parsing in a field

            Corneliu,

            I cannot reproduce the "www2" that you got parsed out. As for the items that come back as both emails and web addresses, maybe it would be wise to remove the search for ".net" on the web part of the script. That means that web addresses would be identified solely by the substrings of "hppt:" or "www:".

            Steve

            Comment


              #36
              RE: text parsing in a field

              Hi Steve,

              Also the foll are not parsed correctly

              email: [email protected] or [email protected]

              -------

              Email: [email protected] or [email protected]

              Regards,
              Corneliu

              Comment


                #37
                RE: text parsing in a field

                Yes, you are right
                after removing the search for ".net" on the web part
                the emails ending in .net were parsed correctly.

                Thanks and regards,
                Corneliu

                Comment


                  #38
                  RE: text parsing in a field

                  Corneliu,

                  With all of the different formats you are encountering, you need to first to establish them all. Deciding on how to approach a problem depends on assumptions made as to how the input data can be laid out.

                  First we assumed that the last word on a given line would be what you wanted and then you came up with examples where that was not the case. First we assumed that the desired substring would be space-delimited and then you showed a case ("Email:[email protected]") to the contrary. First I assumed at most one entity per line and now you show some double entities.

                  This could go on and on but I am not taking any more looks at this unless every possibility is fully documented. If someone else wants to take a look at this they are more than welcome.

                  Steve

                  Comment


                    #39
                    RE: text parsing in a field

                    Hi Steve,

                    You are absolutely right but unfortunatelly I can not control the way the messages I receive are conceived.
                    Unfortunatelly everyone finds a new way to write a message that was never encountered before.
                    However you did a great job and your routine is close to perfection. I am sure that the error percentage is a way under 1% which is absolutely amazing.
                    The slight errors that may occur can be correctly manually.
                    For example I use 3 different intelligent antispam engines working in a chain and even so there are occassions when some spam messages find their way into my mailbox.
                    Thank you very much for all your hard efforts and your patience.

                    One more thing I kindly ask you. Can you show me how to parse the first line of the message to the field COMPANY.
                    In this case it is easy as I will take care
                    that the first line is always the company name and it will always end with a space or CRLF.
                    Just to check that this line is not empty, and does not contain any numbers, or @, or http or www.

                    Regards,
                    Corneliu

                    Comment


                      #40
                      RE: text parsing in a field

                      Hi Steve,

                      Just asking an explanation about the code.

                      in the web searching routine you kept
                      "line_count(emails)". This is the way to be or should it be changed to "webs". The fact is that it is working correctly but I just wish to understand myself.

                      Regards,
                      Corneliu


                      if line_count(emails)"0
                      company_input:website.value = word(word(webs,1,crlf()),-1," ")
                      end if

                      Comment


                        #41
                        RE: text parsing in a field

                        You're right. It should be:

                        if line_count(webs)"0
                        &
                        if line_count(webs)"1

                        Steve

                        Comment


                          #42
                          RE: text parsing in a field

                          OK, thanks again for the beautiful piece of code.
                          Regards,
                          Corneliu

                          Comment

                          Working...
                          X