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 vs. Long Character Field

  • Filter
  • Time
  • Show
Clear All
new posts

  • Memo vs. Long Character Field

    I have become quite paranoid using memo fields and I am redesigning an old app.

    I originally had a flat file type dbase that had about 15 long character fields 200-300 characters and only 2 or 3 were customarily used in each record (all different, not the same 2-3), which left the .dbf records fairly large. I am only dealing with about 10,000 records but I would like to speed things up and hopefully smaller file size would help. I am redesigning to have child records that still need to have a long field, however now there will only be 2 or 3 records attached as children with the long character files instead of having all of the non used fields in the original table.

    So my theoretical question is: Having a single record and with a field needing to type a maximum of 300 characters, but usually its only 30-40 characters, would it be safer to just do a large character field, or have a memo field instead? Your experience and thoughts are greatly appreciated.

  • #2
    Re: Memo vs. Long Character Field

    Character fields only can hold 255 characters and 1 always seems to get lost.
    Memo fields can hold whatever you need(pretty much)
    All memo fields in a table wind up in one .fpt file for the whole table. Lots of memo fields can make the fpt file real big quick.

    If I were doing this and going to use memo fields:
    1. one or 2 memo fields in separate connected tables(set). (Maybe 2 per table if you have a lot)
    2. Create a variable for the user to type into and then save that to the memo field
    3. They would be RTF memo fields - seems to be stronger
    4. Use Pure Text(application) for any copy paste operations so users don't copy garbage into the memo that can hurt it.
    Last edited by DaveM; 11-06-2014, 03:47 PM.
    Dave Mason
    [email protected]
    Skype is dave.mason46


    • #3
      Re: Memo vs. Long Character Field


      Thanks, lets say there is only one memo field per table. Easy to read the memo into a variable and then open an xdialog to edit. How would you programmatically recommend writing it to the field. I have not worked much with RTF fields. Would you just write the value i.e. field.value=variable then save the record, or is there a safer way?


      • #4
        Re: Memo vs. Long Character Field

        A good start is here:
        Dave Mason
        [email protected]
        Skype is dave.mason46


        • #5
          Re: Memo vs. Long Character Field

          Here's something else to look at.

          Alpha 5 Version 11
          AA Build 2999, Build 4269, Current Build
          DBF's and MySql
          Desktop, Web on the Desktop and WEB

          Ron Anusiewicz