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

joining two rtf fields into one

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

    joining two rtf fields into one

    How can I join two RTF fields into one object?
    I can get one RTF field into an rtf object onto a report, but I would like to get two RTF fields into one object on a report.

    When I try and join two RTF fields, the characters at the beginning of the RTF from the second RTF field interferes with the two field joining.

    I know how to populate the object on the report like this:
    t = table.open("nack_letter")
    t.fetch_first()
    ptr_1 = rtf.create(t.Nack1)
    rdata1 = ptr_1.rtf_text
    obj1 = obj("rtf1")
    obj1.rtf.rtf_text = rdata1
    I just can't figure out how to get the second RTF field into that object.
    Thanks.
    Jay
    Jay Talbott
    Lexington, KY


    #2
    Re: joining two rtf fields into one

    Before I try creating something to experiment with, how are you joining the fields? Simple concatenation? What happens if you supply a crlf() in the middle of the concatenation?
    There can be only one.

    Comment


      #3
      Re: joining two rtf fields into one

      Stan,
      Thanks for looking at this.
      I think I am on the brink (of either solving it or going over the edge; hard to tell these days).
      I will post something soon.
      Jay
      Jay Talbott
      Lexington, KY

      Comment


        #4
        Re: joining two rtf fields into one

        Stan,
        Not much luck. My objective is to join two RTF fields into one RTF object on a report, retaining the formatting.
        I can leave a crlf() in the RTF field itself to take care of the blank line, so if I can just concatenate two RTF field contents into one RTF object on a report, that would do it.
        Thanks.
        Jay
        Jay Talbott
        Lexington, KY

        Comment


          #5
          Re: joining two rtf fields into one

          Clumsy and needs tweaking.

          Try

          Code:
          t = table.current()
          h1 = *bin_to_html(t.r1) 'r1 is first rtf field
          h2 = *bin_to_html(t.r2) 'r2 is second rtf field
          h3 = h1+crlf()+h2
          h4 = *html_to_bin(h3)
          h5 = *bin_to_rtf(h4)
          obj1 = obj("rtf1") ' rtf1 is rtf object on report
          obj1.rtf.rtf_text = h5
          I think I am seeing some extra line feeds in my tests. Also not sure if allow growth on print is working.
          There can be only one.

          Comment


            #6
            Re: joining two rtf fields into one

            Stan,
            Thanks. You are correct about the hard returns. My client won't like that, so I am trying to figure out how to get rid of them

            It seems silly to have to go through all these hoops to combine RTF fields. Don't you agree?
            Jay
            Jay Talbott
            Lexington, KY

            Comment


              #7
              Re: joining two rtf fields into one

              My question would be why do they have/need two rtf memo fields that sometimes need to be concatenated?
              There can be only one.

              Comment


                #8
                Re: joining two rtf fields into one

                You could easily combine the contents of 2 RTF's in one with xbasic (I am positive this was asked before) but in this scenario, you simply don't need any xbasic or anything else.

                Simply, place one RTF on top of the other on the report and check the report to eliminate blank lines and the 2 RTF's will be virtually concatenated.

                Comment


                  #9
                  Re: joining two rtf fields into one

                  Stan, fair enough, and here is the answer.
                  I cannot get all of the rtf objects on the report to close up completely, even though I have the "can shrink when printing."
                  I would think the RTF object should completely shrink, but they don't want to do so. Only some of them are closing. I have looked and every one is treated the same.??????
                  I'll try and get a sample together soon.

                  Gabe,
                  I have tried to accomplish this for ours, but some of the rtf objects are not shrinking.
                  Jay
                  Last edited by Jay Talbott; 01-14-2010, 03:45 PM.
                  Jay Talbott
                  Lexington, KY

                  Comment


                    #10
                    Re: joining two rtf fields into one

                    Works for me..
                    Not sure what exactly you are doing?

                    Comment


                      #11
                      Re: joining two rtf fields into one

                      Here's a zipped file of the example.
                      To see the problem, unzip into separate folder, and on the "onPrintInit" event of the report, make sure all of the lines are "un-remmed" out.
                      Then preview the report.
                      All looks fine.
                      Then rem out all lines for obj1.
                      Preview the report. RTF1 shrinks fine.
                      Un-rem out obj1 items and rem out obj2 itmes
                      Preview the report. RTF2 will NOT shrink.
                      Then reverse the positions of RTF1 and RTF2.
                      Un-rem everything and run the report. All is well.
                      Then rem out ojb1 (whose RTF is now in the 2nd position). Preview the report, and RTF1 will not shrink.
                      Do you see this behavior?
                      Thanks.
                      Jay
                      Jay Talbott
                      Lexington, KY

                      Comment


                        #12
                        Re: joining two rtf fields into one

                        Here you go.

                        Comment


                          #13
                          Re: joining two rtf fields into one

                          G.
                          Thanks.
                          But I am actually bringing the values in from another table, based on the field value in the table of the report.
                          I will try and create the report based on the table with the rtf fields and carry the other items from the main table over to the report as variables.
                          Jay
                          Jay Talbott
                          Lexington, KY

                          Comment

                          Working...
                          X