Forum Discussion

ArkadyGranik's avatar
ArkadyGranik
Qrew Cadet
2 years ago

UK currency £ sign not showing

Hello,

This stopped working after a system upgrade a couple of years ago. I can type a £ into a field, but when I save the record it shows as £ (not good) or Ł (acceptable, although not quite right).

Someone suggested to change App Properties to force UTF-8 encoding. However, when I do this exact forms stop working (they no longer pull values from fields and only show field names/codes). There could be other change in behaviour, that I haven't noticed.

Is there a fix for this or a way to show Ł consistently?

Kind regards,

Arkady



------------------------------
Arkady
------------------------------
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    2 years ago

    I have two thoughts.

    1. Can you change your input text field to be Rich Text.  I suggest first make a copy of our text entry field first!! and then changing the text copy field to be type Rich Text.  I think using a rich tax field will solve your issue but I don't know what's going to happen with the current data in what I assume as a regular text data entry field.
       
    2.   or else in view mode display a formula Rich Text fied with this formula

    SearchAndReplace([my data entry field], "Ł",  "&#163")



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------
    • ArkadyGranik's avatar
      ArkadyGranik
      Qrew Cadet
      2 years ago

      Thank you, Mark. Will try and let you know.

      Arkady



      ------------------------------
      Arkady
      ------------------------------
    • ArkadyGranik's avatar
      ArkadyGranik
      Qrew Cadet
      2 years ago

      Hi Mark,

      Rich text seems to be working perfectly, thank you. Ideally, I would prefer to change field type from multi-line text to multi-line rich text. When I do this, QB comes up with the warning about data loss during conversion. 

      Can I loose data in this conversion? If so, is duplicating the original field enough?

      Thanks again,

      Arkady



      ------------------------------
      Arkady
      ------------------------------
      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend
        2 years ago

        You are likely to loose carriage returns.  Suggest that you first copy the multiline text field text field.  When you copy a field not only do you copy the field properties but you copy all the data and all the records in your table for that field. So you have a nice way to get a preview of what would happen if you were to change your main field tips in production now. 

        If there is a pattern where based on the nature of your data you lose certain characters like for example carriage returns then I work around that is to make a formula rich text field which will look for those characters such as 

        \n  (the new line character)

         and using SeachAmndReplace change those to <br><br>

        So,  you keep reworking that search and replace  until you like it and then change probably make a COPY of that field the field and then change the formula field to a Rich Text field type.

        The main thing that you want to protect is your existing data just in case something goes wrong or doesn't work right the first time so make sure that you never convert your actual production field but only convert a copy of it.   

         



        ------------------------------
        Mark Shnier (Your Quickbase Coach)
        mark.shnier@gmail.com
        ------------------------------