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

start "new line" in character field

  • Filter
  • Time
  • Show
Clear All
new posts

  • start "new line" in character field

    I have a 250 character field with word wrap option, but I need to be able to do a "hard return" to start a new line, so it looks like
    so even though I have less than 250 characters (in the above example 14), I can put them in different lines without having to include manual spaces after line 1 to make is start on line 2.
    This is easy in a memo field, all I do is hit "enter" to start a new line, but I can't seem to find a way to do this in a large character field. Any suggestions?
    Kathy McMillan

  • #2
    Re: start "new line" in character field

    Kathy, does the DBF format permit carriage returns in character fields? I think this data type is limited to alphanumeric characters only. -- tom


    • #3
      Re: start "new line" in character field

      Tom, Kathy

      Adding a crlf() to a chararacter field works "somewhat" but I cannot get the field to automatically go to the next "line" as it were.

      I just added this to a button's OnPush event

      dim nam as c
      nam = topparent:myCharacterfield.text
      topparent:myCharacterfield.text=nam + crlf()
      It does for sure add a line but you have to click and doubleclick in the field on the next line to get the mouse cursor to be placed correctly. So am afraid it is just one of those types things that is going to be kludgy and may never work quite right....fiddled around with it too much already! :)

      Note--odd too in that once you add an additional line to the field that would be out of visual sight, Alpha places the list box type scroll bar on the field to be able to see the line(s).
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau


      • #4
        Re: start "new line" in character field

        Mike, I think it's asking for trouble to embed carriage return and line feed characters in simple character fields. Just because something "can" be done doesn't mean it "should" be done. Control code characters are not alphanumeric characters.


        • #5
          Re: start "new line" in character field


          Is this so that a report or letter can display the information in some sort of coherent column?

          If so, then you may want to take the field, and separate the "words" in the field by a space, then on the report, bring the field into a calculated field and then use the strtran() function to convert the spaces to a chr(13). This will move the "words" down in a column of sorts. I would place this calculated field into a rich text field on the report or letter.