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

"Unable to add key to tag" and "hea

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

    "Unable to add key to tag" and "hea

    I was reading the message thread that Graham had posted and I am most unhappy to report that I am getting similar errors.

    When a user is trying to save a form is when I get my error of "Unable to add key to tag" message.

    I am running on a Novell network and there are about 6 users. I have the master copy of a5v4 build 230 and everyone else is using the runtime build 230.


    I need help. Our business cannot operate with this error.

    Thanks,
    Noble

    #2
    RE:

    Noble:

    I'm sorry to inform you that they cannot be fixed
    in 230. They appear fixed in A5v5 beta's, but you
    cannot run production off of a beta especially in light of the fact that they expire after 30 days.

    There are some things that we did to minimize them, and I will search my logs for a response I posted that suggested
    them--almost 3-4 months ago. I will e-mail you it tomorrow.

    Comment


      #3
      RE:

      This (in our case) has always indicated an error with one or more index(es). Most of the times we've received this error it was after a crash of one type or other. Usually rebuilding the indexes fixes it. When that didn't do it, running database compact almost always does. It's not always the index definition, but one or more combinations of data that causes a particular index to mess up. When we've tried these approaches and it didn't fix the problem, the "bad" index was usually removed from the definitions, so make sure you have a copy in another directory to play wih.

      Check are your index definitions. You may have one that looks ok but really isn't. You might try (in a spare copy) removing all the indexes except one and start checking them with rebuild one at a time (ie: after the first builds and you can play around with a new/existing record add the next index). Sometimes switching the order of clauses in a filter can fix it (unfortunately, with 1.5 million records, queries have been too slow for us - if our users don't have instantaneous access to a record, without having to build a new query, it costs us too much time to be a viable product; as far as I know all databases have this speed problem).

      Another thing that can lead to this is scrambled data from a crash. In almost all of our cases where this was the situation one or more memo fields became corrupted (major pain to fix - lots of threads to search to resolve this one).

      I'm not sure, but I've heard that some databases have problems with web servers if they have a null field. Is it possible that a null can adversely affect an index? I haven't noticed this in v4 or v5 beta, but nobody's data can hit all possible combinations that might cause problems.

      Comment

      Working...
      X