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

Convert to RTF

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

  • Convert to RTF

    I feel I should know this but am looking for the best method please.

    I have a table with 15 character fields (80chr long) - the number of fields with data varies from record to record.

    I need to get that data into an RTF Memo field in a new table.

    I have managed so far by appending to a new table into a normal memo field using

    Line1+chr(13)+Line2+chr(13) etc

    And then converting the memo field to an RTF memo field but feel sure there is a more elegant solution out there somewhere.

    Bob Whitaker
    Bob Whitaker


  • #2
    Re: Convert to RTF

    Bob,

    The only thing I might suggest is that you use an alltrim(fieldXX) so that you don't carry all those extra spaces into the memo field.

    If your fields were similarly named, I guess you could use a loop to perform the operation.

    Tom

    Comment


    • #3
      Re: Convert to RTF

      Hi Bob,

      Not sure if this is what you are looking for, INSERT_TEXT_IN_RTF_MEMO().
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment


      • #4
        Re: Convert to RTF

        Thanks Keith I found that - I now have to write some code to gather up the text in the 15 fields - weed out blanks and place in a variable that can use that function.

        Bob
        Bob Whitaker

        Comment


        • #5
          Re: Convert to RTF

          Hi Bob,

          Found the script I used in 2005, created by Jim Chapman.
          Code:
          t=table.open("notes")
          	t.fetch_first()
          
          	t.batch_begin()
          
          while .not. t.fetch_eof()
          	t.change_begin()
          		insert_text_in_rtf_memo(t,"free_text2_rtf",t.free_text_2,1,"arial,10","Black")
          	t.change_end()
          	t.fetch_next()
          end while
          
          t.batch_end()
          t.close()
          
          ui_msg_box("RTF Update","Finished")
          Regards
          Keith Hubert
          Alpha Guild Member
          London.
          KHDB Management Systems
          Skype = keith.hubert


          For your day-to-day Needs, you Need an Alpha Database!

          Comment


          • #6
            Re: Convert to RTF

            And I suggest you NOT use chr(13). Use crlf() instead - which is actually more correct.

            The crlf() is really just a chr(13) and a chr(10) although I don't recall which comes first. (I think it's 13 then 10 but I could be wrong.)

            WHY? Because I used to use chr(13) but found places in v9 where the chr(13) doesn't work. I don't remember where it was but it convinced me to change all my chr(13) uses to a crlf().

            Some background for any young-uns out there:

            "Back in the day" (and apparently still today in some situations) there was a "carriage return" and a "line feed" and both were separate. Sometimes a user wanted just a "carriage return" so they could type over something on the current line - hence no line feed; just a carriage return. (I don't remember why or what program but I remember programming something like this back when I was at Ford.) Or, they might want a line feed without a carriage return so they could type something on the next line at the current location or a few spaces further to the right.

            To go even further back, think about a typewriter. The normal thing to do was to push the "carriage return" lever which rotated the drum one line space (a line feed) at the same time it moved the whole carriage to the right (returning the carriage to it's starting point). However, a light touch on the lever could also be used to simply create a line feed or you could just press on the end of the carriage to return it without adding a line feed.

            Obviously the full "carriage return/line feed" was most common and still is. But sometimes one or the other is all you want.

            HINT: And, since I've discovered that some people have missed this, the crlf() function can take an argument for multiple line feeds - crlf(2) will add a blank line as well as a new line and crlf(3) would add two blank lines, etc.

            I'm pretty sure you can even use crlf(0). I seem to recall running into a situation where I wanted to define the number of new lines with a variable and there were some situations were the variable was actually set to 0 and it worked.

            Disclaimer: I've never tested the crlf() vs. chr(13) in RTF fields but would be shocked if crlf() caused a problem.

            Comment

            Working...
            X