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

A4V6 Page Granular Errors+

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

    A4V6 Page Granular Errors+

    Using Alpha4v6 & now receiving 'page granular errors w/crash adrress' when accessing menu item which then completely kicks user out of app & since run via a batch file w/shortcut properties not set to close on exit, will sit at Dos window indicating 'Finished bat'. No changes to the application have been made except an additional index was added for the top.set. The top.set consist of 8806 records & 16 fields. The menu item runs a macro to use the set & open a form that contains 5 fields of which only 2 are entered by the user. Field rules are set to input data for the other 3 fields via exit triggers which one is for a ref_num that uses DBMAX to get the last # assigned +1. The ref_num is the link in the set commands. The application is used in a multi-user environment & has already been reindexed. Also, when this error happens, it leaves an __A*.tmp file in the user's Alphacon directory & eventhough they reboot the *.tmp file must be deleted manually; plus when one user gets the error then all the users will get the error. The error is only happening for this line item that creates the "header w/ref #" info. Also, there is no a4mem.err file so I do not believe it is a memory issue. This application is run on Dos & Win95 machines.

    Does anyone have any suggestions or experienced the same problem?

    #2
    RE: A4V6 Page Granular Errors+

    happens all the time to me...

    1 problem is win95 memory leakage. the only solution is rebooting regularly, but that is facilitated by a lockup about half the time when i exit netscape.

    another problem is a bad calculated display field or field rule caused by changing something and not updating references in all the other databases. (a.k.a. operator error ) however, i suspect that some of the changes don't get properly propagated across extremely complicated sets - i'd hate to have been the one assigned to write the code for field synchronization!

    Comment


      #3
      RE: A4V6 Page Granular Errors+

      Thanks for the input Jack...I've tried so many things but I am still having problems. There are no caluclated fields on the form but we use a reference number assigned by the "header.dbf" which the next consecutive number achieved through script and index that returns the maximum # in the dbf at present, then this reference number is populated to the "child" databases thus creating a link between them. There are usually several users accessing this application at the same time which shouldn't make a difference but maybe is causing the granular crash error. However, we use this same thing in several of our other applications as well but we are not experiencing the same problems. The majorities of the PCs running this application are DOS machines which I have checked the memory & file handles already.
      Any other suggestions would be much appreciated!

      Comment


        #4
        RE: A4V6 Page Granular Errors+

        Lori,

        I would look at the indexes attached to the database. A corrupt index will cause granular crashes. You may need to slightly redesign a index. I think it's best to use the trim functions.

        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


          #5
          RE: A4V6 Page Granular Errors+

          Along with Ron's logic, I have a partly obscure memory of a FAx On Demand years ago from Alpha about index rebuilding. I've successfully used this several times for corrupt DBF errors and it works.

          Instead of doing the reglar Alpha index update do this....

          Go to each index's 'expression' and position the cursor after the last character; 'back over' it with the backspace key; and then manually replace the character that was removed. Now press F10 to rebuild it. That FAx On Demand indicated that Alpha would genuinely REBUILD the index where the 'stock' 'Update' routine would merely refresh it whatever difference that would make.

          If you think of it, doing that to a record would require a new F10 'Save' - maybe that's what they were saying.

          None-the-less, what can it hurt and.... it has worked for me in the past.

          Write back you successes/failures

          Ken

          Comment

          Working...
          X