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



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


  • Filter
  • Time
  • Show
Clear All
new posts


    I have long experienced shut downs with v4.5 and have tried to identify patterns or a pattern in what is happening when it suddenly gives me the "ERROr! This program has performed an illegal operation and will be suut down. All unsaved...."

    I am using WINDOWS 98 WITH AN AMD333 AND 150MB MEMORY/

    I can not identify any pattern. Sometimes hours or days between shut downs, sometimes minutes. Sometimes while editing a form etc. other times when changing addresses in a mailing list app. Sometimes when I am called away from computer for some reason and return to find the "ERROR!..."

    Any ideas appreciated.


  • #2


    search for related threads in this forum.

    Without more information your question is akin to asking what causes Windows apps to crash?

    I follow a few rules which may be of use:

    1) I avoid multi-tasking alpha five with other large Windows applications, especially during development.

    2) I follow a standard troubleshooting sequence when confronted with an unexplained crash:

    a) verify that Alpha Five is running correctly by playing with the Invoice App that ships with Alpha.

    b) verify that the field rules and data are not the source by entering and editing dummy records in the affected tables or sets using DEFAULT forms. If I can do this, it's often a good indicator that the trouble lies in my forms.

    3) I turn off my Win98 systems every night.

    4) I keep my designs simple, and avoid complex multi-tiered sets, or elaborate memory intensive (graphic filled) forms.

    5) I try to pay attention to what I'm doing, so that when I do have a crash I'm able to give a reasonably complete description of what was going on at the time. I've learned that it helps to quickly jot the description down on paper, too!

    6) I keep a troubleshooting file (actually its a notebook) and when I solve a problem I make an entry which describes the problem and the fix. Helps me avoid (or at least helps me minimize!) the process of re-inventing the wheel.

    -- tom


    • #3
      RE: V4.5 SHUTS DOWN

      Hi John,

      In my case the first thing I would do is press/ctrl/del to see what
      other files are loaded in RAM. The second and possibly more important is to look in "My Computer" and check the percentage of RAM that is unused. When
      the avaliable RAM drops below 70% the system is near locking up. I
      build a lot of computers and remember the days that we were comfortable
      with 1 or 2 megs, today 128M is marginal. I also find that Alpha runs
      much better with 256M, ie, mine has 512M. Memory is cheap these days
      compared to corrupted files, expand yours to 256 or better.


      • #4
        RE: V4.5 SHUTS DOWN


        That first line should read press CTRL-ALT_DEL.


        • #5
          RE: V4.5 SHUTS DOWN

          I've been having this problem ("program has performed an illegal operation and will be shut down") and have been searching this forum. As this is quite a frequent problem on the forum I thought I'd post the solution I eventually found. This cured my particular problem (I was also having to re-boot the machine each time due to the "Licence Exceeded" message on re-starting) but may not cure yours.

          It was simply that I had one line of xBasic, buried in some button code, which wrongly tried to access a record in another table using:
          whereas it should have said:
          You don't, as I'm sure you realise, need the .value.

          As this line was within an IF statement it was only being accessed occasionally which added to the confusion. For some reason this does not result in a recoverable error message, but instead shuts A5 down.

          Just thought I'd log this for anyone else doing a search.


          • #6
            RE: V4.5 SHUTS DOWN

            I had a problem once several months ago where A5 V4.5 would lockup and the only way to recover was to shutdown. I tracked the issue down a report I was designing. I was trying to use a dash line in the report. I would change the dash to a solid line and no lockup. I changed the line back to dash and go to print preview and... instant lockup. I have not had any other lockups. HOPE THIS HELPS.