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

Memo fields problem -- bug ???

  • Filter
  • Time
  • Show
Clear All
new posts

    Memo fields problem -- bug ???

    In my Web App, Memo fields are displaying \ccrr\llff
    when a new sentence is entered. They look like carrage return, line feed control charaters. I'm running Build 1634_3197

    Help -- anybody.

    Re: Memo fields problem -- bug ???

    I have experienced that too, mostly when doing cut and paste.

    Are you having this problem on regular memo fields, html memo fields, or both?

    You should submit this as a bug.

    Pat Bremkamp
    MindKicks Consulting


      Re: Memo fields problem -- bug ???

      This is the problem that Adrian is having, cut down to just a couple components. The main menu is NRmenu.a5w. That will give instructions and show a sample of the ptoblem.

      One memo field works and another does not. If someone sees something obvious, great. Otherwise I will submit as a bug.

      Pat, did you submit as a bug? Any response from Alpha?



        Re: Memo fields problem -- bug ???


        I did not submit it because I have an on-line html editor on that memo field, and I thought it was a bug in that program.

        Now that I see it is an Alpha problem, it should be submitted.

        Since you have a demo, why don't you submit it?

        Pat Bremkamp
        MindKicks Consulting


          Re: Memo fields problem -- bug ???

          Originally posted by Bill Parker View Post
          This is the problem that Adrian is having, cut down to just a couple components. The main menu is NRmenu.a5w. That will give instructions and show a sample of the ptoblem.

          One memo field works and another does not. If someone sees something obvious, great. Otherwise I will submit as a bug.

          Pat, did you submit as a bug? Any response from Alpha?

          For what it's worth, the same things happen in v8..

          edit - still verifying..
          Last edited by Al Buchholz; 08-31-2008, 01:29 PM.
          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


            Re: Memo fields problem -- bug ???

            I have submitted it to Alpha.



              Re: Memo fields problem -- bug ???

              Selwyn identified the problem. Here is his response to the sample.

              Here is what happened.

              1. The 'Impl_rpt_on' field must originally been defined as a RTF Memo field.
              2. The grid component was build and the 'impl_rtp_on' field was selected.
              3. You subsequently changed the table and converted the field to a Memo field. However, this does not cause the grid to be updated.
              So if you were to look in the Xbasic tab in the Grid Builder you would see that the tmpl.fieldInfo[] array lists the type of the field as "R".

              The code that decodes \ccrr\llff into a standard crlf looks for fields of type 'c' or 'm'. Since your field was of type 'r' it never got decoded.

              Had you done this:

              1. press the 'refresh' button on the Grid Builder (next to the prompt for the table name).
              2. deleted the 'impl_rpt_on' field from the grid and then reselected it, its type would have changed from 'R' to 'M' and your grid would have worked ok.

              To solve your problem, just do the above two steps.
              For adventurous people, and if there is a lot of formatting that must be redone if the field is deleted and re-added, I found that changes to the xbasic code in the component to go from "R" to "M" are persistent and solve the problem. There are 3 places that must be changed for each field, 1. the fieldmap, 2&3 are in fieldinfo for the field. The Type property is duplicated twice, so both should be changed.