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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Can't type in a memo field

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Can't type in a memo field

    When I type a character in a memo filed, the character is not saved. The characters just disappear in Ver. 3.04. This problem just started happening. In all other fields, such as character fields, the characters are saved. I would appreciate any help that anyone can give me.
    Tags: None
    #2
    RE: Can't type in a memo field

    Allan,

    There are three possibilities that come to mind for this problem. One is that you have some field rule which is rejecting the Memo Field text, so nothing is what gets written.
    The other possible problem is that the Memo Field entry or its index has become corrupted. Usually the table won't open is this is the case. Do your other memo field entries in the same table look OK? Third, perhaps a second entry of the same memo field will work fine in which case the Form's field entry is corrupted and needs to be removed and replaced.
    You could try to export your data to another identical table and see if those memo fields are better behaved. This may work if your current memo field index is corrupted. Also check the table to see if the field specification has changed by accident.
    You can also try running a Database Compact command which packs the tables and the field rules of old entries. This sometimes fixes bad entries that have dumbed up and refuse to work.

    Dave

    Comment

      #3
      RE: Can't type in a memo field

      Thank you for your response.

      My initial thought was that the memo field became corrupted. I have done the following:
      1. I tried replacing and adding new memo fields.
      2. I tried using the memo fields in the sample sets that Alpha has.
      3. I uninstalled the program and then reinstalled the program.
      4. Took your advice and ran the database compact command.
      5. Checked the field specification, to see if filed specification was changed accidently.

      None of the above worked! It certainly is strange. The memo filed accepts the data entry, but then the entry promptly dissapears when you go to another field or change records.

      My only thoght is that there is something woring with Windows 2000. Any more thoughts.

      Thank you.

      Comment

        #4
        RE: Can't type in a memo field

        Allan,

        Well, this is a tough problem. I've seen similar behavior on other fields, but not with memo fields. I suppose the the first task is to get something that works and then add the pieces of your current system to it until it stops working.
        My rough theory for this problem is that inside the application, Alpha uses tables, indexes, and memos to store the objects that comprise the application. At times some event combinations can cause the indexes to not be updated or Windows can runout of time and not update the indexes. When this happens the application object can become lost or corrupted by an errant write. So you are left with the task of finding the bad object, deleting it and replacing it with a working object.

        The remaining and unchanged areas of your system are the Application files and the Windows OS. I'd guess its most likely to be the Application rather than the OS, but can't be sure. You could try a fresh install of Alpha on a different computer, test that, and then install your App there to find out if the memo field problem magically appears.

        The extended story with the Database Compact and corrupted indexes are that one or more records have to be deleted for the indexes to rebuild. This carries over to the Application objects index, you need to delete one object after copying it to get the internal index to rebuild. The last item is that sometimes two Database Compacts are needed to get the corrupted index keys refreshed by writes in the application files where Alpha looks for index names.

        One of my clients went to Windows NT to much reduce this kind of index corruption. I've also learned to avoid the corruption by editing copies of my database and then paste copies of those to the working application.

        Dave

        Comment

          #5
          RE: Can't type in a memo field

          I have a feeling that it's in the operating system, Windows 2000. I have Alpha loaded on my wife's machine with a simple form made up for her to enter info into the database. She doesn't seem to have the problem. Entries can be made in the memo field. I will try some of your suggestions though, before I do anything with the operating system. I use Symantics Ghost, just in case of problems like this.
          I certainly appreciate all the help you have given me.
          Again...thanks.

          Comment

            #6
            RE: Can't type in a memo field

            Unfortunately...my thought was wrong. It does seem to be the database that is corrupt. I tried to use the same database on another computer, and had the same problems!

            Comment

              #7
              RE: Can't type in a memo field

              Allan,

              OK, so the problem becomes to find the piece of the database that is corrupted and replace it. You can copy and paste most pieces of the database with the windows copy function, only this also copies the corruption present in any of binary files for, say a field or calculation object in a form or report.

              You could copy the affected table to a clean system and see if the memo field problem is still present. If it is, then you can rename it and create an identical new table with the same memo field and field rules. Load this table with the data from the old table and make sure everything is OK with it. Now copy and paste all your old forms and reports to the new table. Check that everything still works.
              ...Since the memo field is the source of the problems, you may find that not all of the memos copy over.

              Next, delete the old table with the bad memo field and run a Compact of the database. Copy and paste the fresh copy of the table to the database and you should be in business again. You'll need to run the Database Compact after copying the fresh table over if you have the table linked into a set. I bet Compact would complain about the missing table!

              Dave

              Comment

                #8
                RE: Can't type in a memo field

                ...A second note is that people who used crash prevention software and antivirus software found they tend to have problems with these because they make the system busy and get in the way of the database which is always doing writes. I don't know if Symantics Ghost is one of these.

                It's also a good idea to save a couple of good working versions of your database in another directory. That way if you do get a corruption problem again, you can export the data to a working object if needed and paste the table, form or field object into the working database easily.

                Dave

                Comment

                Previous template Next
                Working...
                X