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

Access 2007 memo field truncates at 255 chars

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

  • Access 2007 memo field truncates at 255 chars

    Hi

    I'm prototyping an evaluation application to see if Alpha Anywhere is what we want.

    I'm doing this on my desktop machine and running the application server locally. It's convenient for me to use Access as the database, although that will be replaced by MySQL in any production environment.

    I have a query that returns text from a memo field. This returns all the text correctly if I run the query within Access. But if I run it in A5 it is truncated at 255 characters, the normal maximum length of an Access text field.

    Is this an ODBC limitation perhaps? Any help/suggestions welcome.

    Thanks

    John

  • #2
    Re: Access 2007 memo field truncates at 255 chars

    Do you get the same result within the SQL command window? (from the web projects control panel, click on Tools | SQL command window).
    If you do, it is an Alpha issue, if you do not, it is an issue with your grid or your dialog.
    Regards,
    Jay
    Jay Talbott
    Lexington, KY

    Comment


    • #3
      Re: Access 2007 memo field truncates at 255 chars

      Yes, within A5 the result is 255 characters long, within Access the whole field is returned correctly. So it is a fault within A5 I think.

      I'm actually using V12 my mistake so I'll repost there but I suspect the ODBC connector is the cause and that probably affects v11 too.

      Comment


      • #4
        Re: Access 2007 memo field truncates at 255 chars

        I can assure you the A5 doesn't truncate long text fields. It's a bit tough to figure out what you're doing because you've not said how you're viewing the data or getting at the data. Maybe what you're doing seems to truncate but more info is needed.

        Using the Northwind.accdb Access database and the Customers Table, I dropped in a large amount of text into the Address Memo field.

        Then I fired up Alpha Anywhere, latest version, and created an AlphaDAO connection to that database. Now... you mention ODBC but I want to be clear to you want to use an AlphaDAO connection.

        Then I created a Grid, pointed to the connection, pointed to the table, picked the ID, Company, Address. ID and Company are Textbox and Address is TextArea (just 'cause it's prettier, but Textbox is fine too). Then I added another "unbound" Static Text field and I'm writing the length of the Address field to this Static Text field. This is what I get.

        Access mentions that a memo field can hold 65k but that when used in a Web App it truncates at 8k. I'm not seeing that here... and they don't explain the 8k limit... but that's Access for you. I'm mad at Access right now for screwing around with the Object Modified date. As you can see I'm up to 35k in one of the Access records.

        Since you're going to be working with MySQL I wouldn't even bother with testing with Access - they do their own weird stuff sometimes. Stick with testing under MySQL. You don't want to starting working with data... like dates... and find out Access treats them completely different than MySQL does.
        Attached Files

        Comment


        • #5
          Re: Access 2007 memo field truncates at 255 chars

          SOLVED.

          My query used the DISTINCT modifier in SQL. This causes truncation if the query is executed via ODBC.

          No idea why this should happen, but it does. Doh!

          Comment

          Working...
          X