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

Granular Crashes

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

    Granular Crashes

    Hi everyone,

    Maybe I spoke too soon about no granular crashes. We have a couple of Memo fields that we put file information in. A few times after entering further info into one of these fields, the old granular crash occurred. However, instead of sending us out to the desktop, the granular screen freezes on the monitor, and freezes the entire computer as well. The only way to correct this is to re-boot.

    To correct this, we are going back to doing a "C" change and entering some data into a field...then saving it. This stops the crashes.

    Is anyone else having the crashes as well?

    RS

    #2
    RE: Granular Crashes

    Rick,
    If they happen when entering or changing data in a form, granular crashes I found can usually be fixed by the simple method of selecting "o" for options on a form, then "e" for edit,& making a minor alteration to the form, then re-saving the form. This is the only work around I found that works most of the time. Good Luck!

    Comment


      #3
      RE: Granular Crashes

      Hi Rick

      I was having this problem as well. I was able to fix it permanently with this script. Its run from a custom menu choice.

      {ONKEY�"{F10}",�{}}
      {screenfreeze}
      c

      {*** "pgdn" is here because my memo field is on the second page of a form ***}

      {PGDN}
      {ALTM}

      {*** the "datstamp" script just inserts the current date in front of all previous entries for this memo and positions the cursor next to it for your text and unfreezes the screen ***}

      {play�"DATSTAMP"}

      Hope this helps

      Robert

      Comment


        #4
        RE: Granular Crashes

        I am also experiencing granular crashes when entering data into a memo field. My computer doesn't freeze though. I just get kicked out of Alpha. Have you come up with any solutions? I wonder if they are working on a patch. I use memo fields all the time and find this annoying.

        Comment


          #5
          RE: Granular Crashes

          Hi Michelle

          The only way I know to get rid of the problem compeletely is to use the key strokes above, either manually or in a script.

          You go into change mode and then open the memo field.

          c
          {alt-M}

          Robert

          Comment


            #6
            RE: Granular Crashes

            I contacted tech support with this problem and they sent me the most current A4V7 cd with the slipstream release to see if it would help with this bug. So far it has. I have not had one granular crash in 2 days. You can also download a copy. Good luck.

            Michelle

            Comment

            Working...
            X