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 CRASH W/SUBFORMS

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

  • GRANULAR CRASH W/SUBFORMS

    I am getting a granular crash error...


    everytime I go to view enter and I use the layout that has tabbed subforms I crash...

    It worked fine for a little while, I added a couple tabs on the subform and played with the colors a little bit.

    Can anyone help here ???


    PS. I have taken 2 of the tabs off and changed colors back and it still crashes... ??


    Kindest regards



    Samer N. Gorial

  • #2
    RE: GRANULAR CRASH W/SUBFORMS

    Undoubtedly, the solution I finally used to prevent granular crashes is a last resort. I removed all calculations from forms I use for inputing data by adding calculated fields to the set's (or database's) field rules.
    Zero granular crashes since.
    Joe

    Comment


    • #3
      RE: GRANULAR CRASH W/SUBFORMS

      As indicated in one of the responses to your question, forms often generate granular crashes. However, often you must use forms with calculated fields.

      We use tabbed subforms in many of our sets. They all contain large quantities of calculated fields. You mention that the crash happens as soon as you View-Enter. Is this happening when you first start to use the database?

      If it is, there might be a workaround that will help. It worked here in a very large complex set we use for order processing.

      We use the Autoexec script to open up the problem database, then immediately move to another database, then move back to the problem database. For some reason, and I do not know the reason, this prevents the granular crash. Our experience has been that the granular crash happens only when entering the first new record. If you use this routine you might fake out the crash with the activity and be able to continue using complex subforms without a problem. Don't ask me why this works, but I can assure you that it solved a major problem here.


      Al Cain

      Comment


      • #4
        RE: GRANULAR CRASH W/SUBFORMS

        My experience has been that granular crashes are mostly related to faulty logic in a calc field, except the ones that aren't. Some can't be explained.
        We keep a fresh copy of the runtime with all the udn's on the server. Sometimes I find that nothing seems to fix A4 on some workstations except reloading the executables and udn's etc from the server. This is no big deal, all I do is drag over a copy of the directory from the server to the client. This solves a lot of problems.

        Sometimes granular crashes come and go for no apparent reason.
        I think its the nature of the beast.

        Russ

        Comment

        Working...
        X