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



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

Font issue on RTF Field

  • Filter
  • Time
  • Show
Clear All
new posts

  • Font issue on RTF Field

    Good morning,

    I needed to change a field type from CHARACTER to RICH FORMAT for text formatting purposes. That seemed to work fine but now, I cannot change the font of the field on the report.

    The 8 pt ARIAL default, is not large enough and I cannot change the font size. Other fields on the report are fine.

    Does anyone have an idea of why the field will not allow me to change the font type or size ?



  • #2
    Re: Font issue on RTF Field

    The formatting for the rtf memo field is stored along with the actual text. As such it cannot be overridden by formatting the field on a report.

    Example rtf memo field contents:

    "{\rtf1\ansi \deff0{\colortbl;\red0\green0\blue0;\red255\green0\blue0;}{\fonttbl{\f0\fswiss Tahoma;}{\f1\fswiss Tahoma;}{\f2\fnil Tahoma;}}{{\f1 \cf1 \fs16 Some}{\f2 \cf1 \fs30  }{\f2 \cf2 \fs44 text}}}"
    In the above, fs is the font size operator, doubled from the actual setting in the field (no clue why it is doubled).

    If the field has a standard font size in all records and you wanted to preprocess the table before printing the report you could....

    tbl ="atest",FILE_RW_EXCLUSIVE) 'change attest to your table name
    while .not. tbl.fetch_eof()
    rtftext = *bin_to_rtf(tbl.rtfmem) 'change 'rtfmem to your rtf memo field name
    newrtf= strtran(rtftext,"fs16","fs48") 'change font size 8 to 24 'set 16 and 48 to double actual standard size and double new desired size
    newbin = *rtf_to_bin(newrtf)
    tbl.RTFMEM = newbin
    end while
    To reverse the changes after the report is printed just reverse the values in the strtran()

    newrtf= strtran(rtftext,"fs48","fs16")
    Last edited by Stan Mathews; 06-19-2018, 12:07 PM.
    There can be only one.


    • #3
      Re: Font issue on RTF Field

      Stan 06202018.pdfStan,

      No luck so, I looked at the *PLAIN_TO_RTF operation. Here's a copy of the operation: (see attached)

      I exported the file into CHARATER. Thinking I could IMPORT the TEXT field into RTF. But no. So, I thought I would reintroduce the original problem as maybe I did not do that yesterday.

      I would like to be able to load the CHARACTER field into the NEWRTF format field and be able to change the font on the report as I would like.

      Does that make sense ?



      • #4
        Re: Font issue on RTF Field

        Not really.

        The script I provided will change the font size in the current rtf memo field for all records based on the two numbers supplied to the strtran(), no extra fields needed. After running the report using the new font sizes you can then reverse the numbers in the strtan() to set the font size back to the original. If you don't want the original font size restored just don't run the reverse.

        The data in an rtf memo field is not stored as rtf, it is stored as binary.

        The expression to take a plain text field and place it in an rtf memo field would be


        but it won't solve your problem. It will still have embedded rtf font size, etc - whatever your system defaults are.
        Last edited by Stan Mathews; 06-20-2018, 03:23 PM.
        There can be only one.


        • #5
          How can I load a RTF Field weith data from a CHARACTER field ?

          That's pretty much the entire post.

          I have a file with a field that needs to be RTF MEMO. I can export it, I can change field type to MEMO, etc... but, I cannot get the field type to RTF MEMO such that I can change the font size on a report.

          When I place the field on a report, I change the size of the font but, the actual report does not reflect this change.

          If I change the field to MEMO, all is fine but, I cannot highlight and change the attributes (i.e. UNDERLINE, BOLD, etc.) of a portion of the record, as I wanted, and that needs to happen.

          Stan had some suggestions but I couldn't get the data to respond properly.

          Any ideas ???



          • #6
            Re: How can I load a RTF Field weith data from a CHARACTER field ?

            You can't.

            You can add a plain memo field to your table. Edit the table field rules and create a cansaverecord event for the rtf memo field.

            tbl = table.current()
            tbl.plmem = *RTF_TO_PLAIN(*BIN_TO_RTF(tbl.RTFMEM))

            where plmem is the plain memo fieldname and rtfmem is the rtf memo field name.

            All edits to the rtf memo field will be copied to the plain memo field, text only. You can place the plain memo field on your report and format as desired.

            To populate the plain memo field in current records with the rtf memo text contents you can run an update operation.


            There can be only one.


            • #7
              Re: Font issue on RTF Field

              2 threads merged since the second is a continuation.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein