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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Comma or Period after field in RTF

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Comma or Period after field in RTF

    EVERY time I end a field in an RTF box with a comma or period I get random changing text in the rest of the RTF box. Put a semi-colon after it and it doesn't happen. Am I missing something I shouldn't be doing?
    Tags: None
    #2
    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 table with a minimum of records (and its support files, zipped together) will make it much easier to diagnose the issue.

    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.

    Comment

      #3
      Originally posted by gyoung
      EVERY time I end a field in an RTF box with a comma or period I get random changing text in the rest of the RTF box. Put a semi-colon after it and it doesn't happen. Am I missing something I shouldn't be doing?
      What Tom said. I can't duplicate.

      Comment

        #4
        OK, here is a test database Selwyn sent me. It shows up in here also. Go to the reports tab, select the test report and open it up with design. Double click on the RTF box to edit it. After the "driver" field on line 3, add or change the character, like put a period there. Do a print preview and see all the driver text on each line.

        Even before you do a print preview look at the beginning character of each line. They change and appear as a field character everytime you change the character after the field "Driver" as my example shows.

        I am using A5V6 build 1614 version 2058.

        George

        Comment

          #5
          George,

          I took a look. The text you've inserted into the RTF object appears to contain illegal characters, which are displayed in gray, along the left margin in virtually all lines below the line that contains your Driver field.

          How did you put the text into the RTF field? I'll wager you did not type it there, did you?

          -- tom

          Comment

            #6
            Sorry, really did type them in there, NO cut and paste. When I inserted the field code those characters appear. That's the problem I am having. Sometimes when I change the period or comma after the field code the random characters go away bu thenselves. Try cleaning it up and inserting a field code yourself. By the way, this is a test database Selwyn sent me so it is as clean as it can be.

            George

            Comment

              #7
              Revised report

              George,

              You must be doing something differently than me.

              Unzip the attachment to an empty folder. Open the TomsTest report. After removing your illegal characters I had no problem inserting fields from your table.

              I inserted them by dragging and dropping the fields from the Drag/drop list. (Available on the View menu while in Design mode). Is this how you do it?

              -- tom

              Comment

                #8
                2nd Revised report

                And, here's another version. This time I've added both commas and periods immediately following the table fields.

                I'm unable to replicate the issue you see. Continue to think you're doing something differently. Please confirm your Alpha Five build number. (on Help menu, About Alpha Five).

                -- tom

                Comment

                  #9
                  Thanks Tom. I used your test report and inserted a field. Yes I also just drag and drop it. It worked OK.

                  I went back to my report and could not remove the illegal characters until I removed the "Driver" field.

                  I tried this on two different computers. Same database. Same results. Weird.

                  Thanks, I am still looking into it. To me it's very repeatable and I thought it was my database so when I went to the one Selwyn sent me I ruled that out. I have a different version of A5V6 that Selwyn also sent me but I had this problem months ago but had a cheap work around then.

                  George

                  Comment

                    #10
                    Here is a screen shot of the about Alpha 5 V6. But like I said, I have had problems with this for months but always got around it. Not something I like learning.

                    George

                    Comment

                      #11
                      Build 1600-2057 ?

                      -- t

                      Comment

                        #12
                        No, it's 1614-2058.

                        george

                        Comment

                          #13
                          Guess I'm not the one to try to help you. Build 1600-2057 seems to be the latest public release.

                          -- tom

                          Comment

                            #14
                            Problem solved. Tom thanks for your help. Selwyn just confirmed my bug report and the fix will appear in the v7 release.

                            george

                            Comment

                            Previous template Next
                            Working...
                            X