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

Memo screen object error in v10 not in V9.

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

  • Memo screen object error in v10 not in V9.

    I need some help here. I have an application in v9 that creates text for a memo field. The v9 application runs fine. When I move it to v10 I get a "funky" characters displayed on the screen when I go longer than say 200 characters. Again I stress that the program works great in v9.

    The field is a object pointing to a memo field in a table. I load the field by putting other memo fields together from another table. The program works ok on first touch of a button that performs this action, but on subsequent button pushes it places special characters in the field and then the field type changes.

    Any suggestions? On v10 build 2814, system addins build 3539.

  • #2
    Re: Memo screen object error in v10 not in V9.

    Hi Bob,

    Welcome to Alpha.

    It might help better on this occasion if you were to post a sample of your app with the problem forms.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


    • #3
      Re: Memo screen object error in v10 not in V9.

      You can test this error quite easily. I have a form pointing to a memo field in a table. I also put a field on the form for the length of that field and calculated it. I then added characters to that field and redisplay it.

      'script_play_local("notes_exam") I comment this line out because I was loading the texam from a script

      parentform:Obj_exam.value = parentform:Obj_exam.value + "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      parentform:Obj_exam.value = parentform:Obj_exam.value + "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

      'parentform:Obj_exam.value = texam
      parentform:tlen.value = len(parentform:Obj_exam.value)

      When the field parentform:obj_exam.value goes above 1050 characters it resets to "". In v9 it continues to display the field even when length went past 3000.

      Hope that clarifies things.

      Comment


      • #4
        Re: Memo screen object error in v10 not in V9.

        Bob, your description is better, but still not as good as supplying a working copy for us to see.

        Here's what I think you're doing, and it seems to work fine in build 2890_3545.

        Does it work ok for you?

        Comment


        • #5
          Re: Memo screen object error in v10 not in V9.

          Ttanks Tom. This is a chiropractic notes package. I will have to pull out senitive data and zip it for all to look at. I will also try build you are talking about to see if it has same error. Sorry I am very new at posting and am unsure what I should include (file wise).

          Comment


          • #6
            Re: Memo screen object error in v10 not in V9.

            Bob, if you copy the entire database to a new folder, you could then open it there and delete or mangle the data to your heart's content. We don't need to see "live" data, nor do we need all the records, just a representative sampling. Alpha includes a Zip tool that can be used to create a "zip" file containing the entire database. This can be uploaded when replying to a message here. Use the "Go Advanced" button to open the advanced message editor. "Manage Attachments" is an option in the advanced editior.

            Comment


            • #7
              Re: Memo screen object error in v10 not in V9.

              Tom,

              you used
              parentform:notes.text = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

              which doesn't generate the error.


              I was using
              parentform:notes.value = "XXXXXXXXXXXXXXXXXXXXXXXXXXX"
              which generates the error even in your example in v10.

              So the question now becomes why do we have the two different forms? (ie. .text and .value) and why the change in v9 to v10?

              Thanks for your example it helped immensely?

              Comment


              • #8
                Re: Memo screen object error in v10 not in V9.

                Oh by the way I used the .value form of the xbasic command because when I added an action script to the button I used >set field values< which then placed that code into xbasic. I assumed since the code worked that it was the proper way to perform that programming step. Obviously I was mistaken.

                Comment


                • #9
                  Re: Memo screen object error in v10 not in V9.

                  Bob,

                  I don't have a complete answer for you.

                  Code:
                  .text
                  is a reference to the "text" property of the "notes" object in the form layout. This is the "text" equivalent of keystrokes entered from the keyboard. That's why I chose it here.

                  Code:
                  .value
                  is a reference to the "value" property of the "notes" object in the form layout. This is the data-typed "value" held in the record buffer for the field.

                  It's my understanding inputs from the user are actually stored in two places. First the text box receiving the keystrokes, and then the data-typed buffer to which the text box is bound. Normally, the buffer stays in synch with the text box. I suspect something has changed which is causing a problem for you in this special case.

                  I've submitted a bug report.
                  Last edited by Tom Cone Jr; 05-21-2010, 05:37 AM.

                  Comment


                  • #10
                    Re: Memo screen object error in v10 not in V9.

                    Tom,

                    Thanks. Your explanation helps. At least I have a working step now in Alpha 5v10. Thanks for the bug submission as well.

                    Comment


                    • #11
                      Re: Memo screen object error in v10 not in V9.

                      .text only has unformatted text

                      .value has formatting information embedded. Those are the 'funky' characters that you are seeing.

                      Comment


                      • #12
                        Re: Memo screen object error in v10 not in V9.

                        Bob, I've been informed that a bug was found and squashed. Should be in a future release candidate.

                        Comment


                        • #13
                          Re: Memo screen object error in v10 not in V9.

                          Tom,

                          Thanks for bug submission, help squashing, and general info I will most likely have future posts. I use the ontimer feature and it seems it has a few quirks with embedded browses. I was hoping upgrading to v10 helps. We will see. Thanks again for the hard work you and others do. It helps us naive old and young part time programmers.

                          Bob Nilles

                          Comment

                          Working...
                          X