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

Removing Carriage Return or Line Feed in a Memo field

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

    #16
    Re: Removing Carriage Return or Line Feed in a Memo field

    Instead of strtran()
    use:
    strtran_multi()
    Or, use regex

    Comment


      #17
      Re: Removing Carriage Return or Line Feed in a Memo field

      Backing the trolley up.
      Situation. An application built in SQLServer2008 has a field in one of the tables which is a "comments" field.
      This is VarChar 255.
      A process extracts the data from several tables and formats it in text blocks - no delimiters, like this;

      A12345TedGiles Cedar Lodge Peppin Lane Fotherby 9999.99 9999.99 AP CL 20150114

      It all works on byte position start and end.

      My problem is that the comments field allows a Carriage Return and the extract process interprets this as the start of a new line and starts a new line with the remaining data.
      This is not my design, it is a major suppliers design in the social care software market.
      The extracted file is flawed, so when it is imported into Oracle Financials, there are lines which fail.
      The supplier is not good at resolving problems like this and say it is a user issue "stop them hitting enter", which as they are NOT computer literate won't work. What is being done is that the extracted files are being examined manually and the CR's removed. It really is a simple process, but it takes 2 people nearly full time to correct these problems with the extracts. There are other simple issue I can fix using AS, but I had hoped - and I will try Stan's upload - to import the text file into AS, use a Memo field to examine the text in the Comments field and remove the CR's.

      It is entirely possible that I have misunderstood Stan's suggestion so I'm off to try it now.

      Oh, by the way, Oracle doesn't want to import � signs so they have to go too.

      Edit:
      It was me Stan, trying too hard with the code. Your kind example set me straight.
      Now to see if I can get them to adopt it!
      Last edited by Ted Giles; 01-14-2015, 07:10 AM.
      See our Hybrid Option here;
      https://hybridapps.example-software.com/


      Apologies to anyone I haven't managed to upset yet.
      You are held in a queue and I will get to you soon.

      Comment


        #18
        Re: Removing Carriage Return or Line Feed in a Memo field

        I don't see why they need to adopt it.
        You have a form with a button that runs the operation to import the extract into a table with a memo field? The button uses action scripting to run the operation? Add an inline xbasic element which executes the function on the imported table.
        There can be only one.

        Comment


          #19
          Re: Removing Carriage Return or Line Feed in a Memo field

          I'm dealing with Government Stan.
          They all need to be consulted just in case there is a more convoluted and expensive way of doing something.
          With your help, and the others who chipped in, it took about 1� hours to put a form together with the options for removing CR's and spaces, swapping - and + signs, adding a unique qualifier to a field and laying it out nicely.

          Importing, processing and Formatting the output will probably take a bit longer as the files will need some pre-processing I'm sure.
          They have a "wealth of BizTalk experience" it has been said, so maybe they want to go for the long winded and approved version as opposed to me and my Alpha toolkit.
          Story of my life.
          However on a separate subject, I have built them an installable data Dictionary which they have to get from my server, so we'll see what happens.


          My next hurdle is removing Chr(156) � sign. I put it in the function but it is being ignored.

          eval("tbl."+fieldname) = strtran(eval("tbl."+fieldname),chr(156),"")

          Any ideas?
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment


            #20
            Re: Removing Carriage Return or Line Feed in a Memo field

            Try

            eval("tbl."+fieldname) = strtran(eval("tbl."+fieldname),chr(163),"")
            There can be only one.

            Comment


              #21
              Re: Removing Carriage Return or Line Feed in a Memo field

              That did it.
              Alt 156 creates a � Alt 163 creates �
              Chr(156) won't remove it, Chr(163) will remove it.
              Thanks Stan.
              See our Hybrid Option here;
              https://hybridapps.example-software.com/


              Apologies to anyone I haven't managed to upset yet.
              You are held in a queue and I will get to you soon.

              Comment


                #22
                Re: Removing Carriage Return or Line Feed in a Memo field

                Confusing to me as well

                ? chr(163)
                = "�"

                ? asc("�")
                = -93
                There can be only one.

                Comment


                  #23
                  Re: Removing Carriage Return or Line Feed in a Memo field

                  ? asc("�", .t.)
                  = 163
                  Jo Hulsen
                  Dommel Valley Solutions
                  The Netherlands

                  Comment


                    #24
                    Re: Removing Carriage Return or Line Feed in a Memo field

                    Why the need for [.t.] Jo?
                    Also, can I put an Octal or Hex value in as a replacement?
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    Apologies to anyone I haven't managed to upset yet.
                    You are held in a queue and I will get to you soon.

                    Comment


                      #25
                      Re: Removing Carriage Return or Line Feed in a Memo field

                      Ted,
                      Please check the wiki for the asc function. The .T. returns a positive number for high-order characters.
                      As for Octal or Hex values, I did try but didn't find a possibility.
                      Jo Hulsen
                      Dommel Valley Solutions
                      The Netherlands

                      Comment


                        #26
                        Re: Removing Carriage Return or Line Feed in a Memo field

                        Also, can I put an Octal or Hex value in as a replacement?
                        No, but you can convert on the fly.

                        ? chr(*from_hexn("A3"))
                        = "�"
                        There can be only one.

                        Comment

                        Working...
                        X