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

Another cause for granular crashes

  • Filter
  • Time
  • Show
Clear All
new posts

  • Another cause for granular crashes

    I thought I would mention a "new"? cause for them, in case you haven't got enough! First, I'm running A4v6 under win98, second attempt. I have a form within a set that has a memo field included, in the opened/displayed mode. If you come into a record without making any changes and decide to double click on the memo, in order to make some changes with the memo editor, when you are done and close the editor with F10, you're going to go off to granular crash land, every time.

    The work around is to always remember to make a dummy change while in the same record, before you enter the memo editor. Just hit "C", click on any field, then hit F10.

    I am running the Thomas & Pytel DOS extender, something mentioned several times here, and I would highly recommend it, if you haven't already switched.

    Sorry, the email addy above is ancient, can't seem to get Alpha to let me update it.

  • #2
    RE: Another cause for granular crashes

    Hi Al,

    We have also experienced the granular crashes when trying to edit and save a memo field. We have also found (by accident) that if you simply go into any field in the dbf and make a minor change like add a period or something it... you can then go and work in any memo field for that record and not have a crash.

    We made a dummy field like you did, put it at the top of the form and made it first to be entered (it can be 1 character long).

    It's like it re-attatches the memo field(s) with that particular record (or something).

    It is now standard operating proceedure with our staff, and we have not had nearly as many crashes as we were having before. In fact, the only time we have had a crash since, has been when we have forgotten to do this proceedure.

    I have found (at least for us), that you have to change data in any field and not just press "C" and then F10. If that works for you have to go with what works.

    I thought I would add my experiences to yours Al, in case someone had a problem like ours.

    Regards to you and all,



    • #3
      RE: Another cause for granular crashes

      The DOS extender mentioned can be found here:

      Doug Allison


      • #4
        RE: Another cause for granular crashes

        Hi Rick
        My Invoicing set crashed every time I went into a certain form. Just started doing it one day .

        So I copied a similar form, modified it to be 'exactly' like the 'flawed' form, and have had no trouble since.

        How did that form get 'corruted'?


        • #5
          RE: Another cause for granular crashes

          Hi Doug.

          Your guess is as good as mine. Gee I hope that doesn't happen to me. My forms are quite complicated with calculated fields and all. If it corrected the problem, great.




          • #6
            RE: Another cause for granular crashes

            I have been having form crashes on a form that has a memo, but not when the memo is going to be updated.

            Last night (Sunday evening) I created a form rebuild script for the one application that errases the form and recreates it for the end user. Fortunately, this was not a complicated form. The problem is that the script will not accept buttons - those have to be done manually.


            • #7
              RE: Another cause for granular crashes

              What is a DOS extender and what does it do. Id there any particular way to install it once you get it? I have problems with Granular crashes and I would love to find a solution.


              • #8
                RE: Another cause for granular crashes


                What operating system are using with Alpha Four Version Six?

                I ask because version Seven has been released to overcome similar problems with newer operating systems (XP and 2000, in particular).

                - tom


                • #9
                  RE: Another cause for granular crashes

                  We are using windows 98. Any idea what a DOS extender is and how it can help with this problem?


                  • #10
                    RE: Another cause for granular crashes

                    I used A4v6 under WIN95 for my business's stock/invoicing application and experienced regular granular crashes early on. The worst offender was my stock form which was had 4 tabs and an awful lot of calculated fields. I got rid of the tabs which showed me sales, purchase info etc. and installed buttons to switch to other sets for the same info. I still got (fewer) crashes. Then, I deleted many calc fields and generally simplified the form. The granular crashes lessened and then stopped as the form got simpler so I believe that simplification might be the answer to your problem.

                    We still experienced the occasional problem for example, when entering this stock set, the form would appear and one of the calc fields for the form would play out as a series of keystrokes. Weird!! This meant that when the first 'e' in the expression was reached, Alpha went into Enter mode and the rest of the keystrokes were entered into the first field of the set (this is how I worked out it was a calc field from the form). This problem stopped when we changed to Version7. We have experienced no problems since. Version7 seems much happier under Windows.


                    • #11
                      RE: Another cause for granular crashes

                      Do there have to be form rebuilds with version 7? Or can one just go there from version 6?