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 Crash Relating to Indexes

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

    Granular Crash Relating to Indexes

    I have posted this message before on this message board but I have never gotten an answer.

    In a set with many indexes, I have a script which is used to print records starting at the current record. It begins by placing the set in the Order Number index, since we print orders consecutively starting with the first one in a new group.

    It works fine except if immediately before running the script a search (find) was conducted using another index, and that index is still active at time of running the script. What happens is that the script moves the set to the Order Number index before issuing the print command. But for some reason the set is not properly in the Order Number index.

    If I do this manually it still happens.

    Does anyone have any idea why this happens? It seems that the set does not really move into the new index simply because it is set in that index. It needs to either have a new order entered or a search done in the Order Number index before it works properly.

    #2
    RE: Granular Crash Relating to Indexes

    I suspect your problem is the search.

    I have a set that crashes at times. The crash is caused by a defined search. Somehow the search gets corrupted and causes the program to crash.

    I edit the search, not changing a thing, and everything runs fine.

    As I rewrite this, I may try deleting the saved search and use a script to run a onetime search.

    Ron
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    Comment


      #3
      RE: Granular Crash Relating to Indexes

      I recently have experienced a Page Granular error & then kicked out of application. I am running A4V6 & this application has been running for years but in the last few weeks I have been getting this error only when the user selects a menu option that creates 'header' information which includes a ref num which is the link to the other tables via a form. The field rules use exit triggers scripts that populates the current date, a variable that represents the user's area along with specifying what index to use when the other menu item is selected to edit the 'header' information so will only display the data for the user's area. However for this script I am using the 'letter' of the index instead of the index name which I wondered might be a problem since there are now 13 indexes & several have a filter expression specified. I had reindexed but still had a problem and also verified that no corruption existed which none was apparent. Also since this is used in a multi-user environment it is creating & leaving a temp file in the user's Alphacon directory; plus once one user gets the error then all the users get the error. I plan on recreating the form to see if it got corrupt somehow when users are not accessing the app. I too am at a loss what might be the problem -- I have a posting for 10/29/02.

      Comment

      Working...
      X