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

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

Truncated Field Names (:<<((((

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Truncated Field Names (:<<((((

    FYI..................

    I have been experiencing a nightmare. Working feverously on a database, up against a deadline and data is randomly missing after an append. One time it's this field and the next another field. This last time it was 10-12 fields.

    I tracked the problem to truncated field names in the tables the append is coming from, truncating the names to 10 characters. Did a search and this is what Jerry Brightbill had to say:

    "The truncation of the names to 10 characters is not new and has been around since the early versions of a5v4. The problem is predicting what actions will cause it. Some have been mentioned, but the best solution is to just use 10 characters. The same issue effects field names, but truncation here is more rare, but can happen."

    If it's rare, it's happening to me so the only thing I can do is reduce all field names to 10 characters or less.

    Wonder if anyone has a solution other than reducing to 10 characters? Or any other suggestions. I'm all eyes and ears.

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Truncated Field Names (:&lt;&lt;((((

    Hi Ken,

    Yes, I too have seen the field name truncation, although rarely. Could you use a 10 character field name - and use the Field Rules "Default Descriptive Name"? That way, when you drag fields to forms, the long "name" will display, but the actual name will be 10 characters long.

    Peter
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      RE: Truncated Field Names (:&lt;&lt;((((

      Hi Peter,

      Yes, I'm wading through the swamp of changes. Wouldn't it be nice if A5 changed the field names in the forms, etc., automatically? I sure hope this is fix in v5.

      kenn
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment


        #4
        RE: Truncated Field Names (:&lt;&lt;((((

        I have experienced truncated field names occasionally,
        if I visit a client and zip up their runtime data, and transfer to my laptop so that I can work on any changes using the full version.

        Once on my computer, if I unzip the data and then add the tables into a different database, long field names get truncated.

        So now I always add the unzipped tables into a copy of the same database.

        Michael

        Comment


          #5
          RE: Truncated Field Names (:&lt;&lt;((((

          Michael,

          The long fieldnames are not stored in the DBF files. They're in the dictionary files, cause the DBF format limited fieldnames to 10 chars. Your 'new' database doesn't see the former dictionaries, so the fieldnames get truncated to the values actually stored in the DBF. Next time, copy over the dictionary files, too. -- tom

          Comment


            #6
            RE: Truncated Field Names (:&lt;&lt;((((

            Tom,

            This is exactly what my client is doing. Thanks for solving the problem!!

            Kenn
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment

            Working...
            X