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

Return of the granular crash-after p-mode

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

    Return of the granular crash-after p-mode

    I have A4V6 running on NT Server with 5 user pack license
    and 5 users. The Set is full of calculations and indices.
    A Granular crash would occur when designing a set or DBF
    on occasion so thanks to the helpful folks on this board we
    installed the P-Mode Extender on the server. Our Set is on the server. It seems now we are having more crashes than ever. They are occurring on the memo screen. We can type the note fine, but when we hit F10 to save we get a granular crash. Sometimes I can go back into the program and the note is there. More recently the note is gone and it is happening more often. Today We couldn't alt-M to any record at all. I rebooted the server and it allowed us to post notes again. But now it is crashing again. re-install the DOS extender? Anyone else have this problem? Thanks, cathy

    #2
    RE: Return of the granular crash-after p-mode

    I am having this problem when I go to print a browse table, same thing basically, it works fine untill I hit f10 and then the granular crash screen appears????

    I have no clue what to do.... if you ever figure it out please let me know.


    Samer N. Gorial

    [email protected]

    Comment


      #3
      RE: Return of the granular crash-after p-mode

      Mr. Gorial,

      Thanks for the reply- I'm going to have the extender
      removed from the winNT server to see if we have less of a problem. My thinking is if I want to reconfigure or
      "program" something I'll do it on my own station-maybe I'll install p/mode there since thats where they say it works-on
      single stations. I'll hope for the best on the server.

      I'll let you know how I make out.

      Cathy

      Comment


        #4
        RE: Return of the granular crash-after p-mode

        for what ever this information is worth, I must tell you.... we overcame our granular crash "somewhat".

        We were printing a browse table, while printing we would choose the primary index to be "time" and we would select "all deleted" records in the database

        We exported the records that we wanted to print to a copy of the same database..... so we have a databse copy of the same data and fields with only the records that we want to print only this eliminates the need to choose (all deleted)
        when printing from the browse table.

        Printing then from th browse table we only printed by (time field) so that it would be less complex for alpha to print, and it printed fine with no granular crash until the end if we pressed F10... it doesnt always crash and sometimes we can just press escape before we press the last f10 to print.

        I dont know if this helps you any, but I hope it does.


        Good Luck!


        Samer N. Gorial

        Comment


          #5
          RE: Return of the granular crash-after p-mode

          Mr. Gorial-

          We have to use f10 to save the notes on our memo page. I had the dos extender removed from the network server, however we had the crashes the same as before. I shut down the serever(not always convenient since we have 5 users in two different departments) but it does seem to clear it up for a while. There are probably work arounds to it- i have single line notes in another(child) database that we can use, but the memo page is so easy-its just too bad it doesnt work all the time. Im glad you found a way around your situation.

          Thanks for the suggestion, though.
          Cathy

          Comment


            #6
            RE: Return of the granular crash-after p-mode

            ???? thats very strange ????

            I have never encountered anything like this. If I hear of anything or think of anything I will get back with you.

            If I could ask though?, I understand it is a memo field, I wonder if you add another memo field to the record just to see if the same thing happens again with the second memop field in place.... or I would try copying the database and see if it still happens in a differently named database ?? if you have not already tried it.

            With alpha I have found process of elimination has helped overcome most problems...

            once again good luck...

            Comment


              #7
              RE: Return of the granular crash-after p-mode

              My experience has been that granular crashes are due to problems with field rules but sometimes are hard to pinpoint. As far as the memo field is concerned you will find that over the long haul you will have better luck putting the memo field in a separate dbf with a linking field. To enter a memo have a script open the linked dbf, put in the link and play alt-m. The problem with memo fields is they are occasionally prone to corruption. If the memo is corrupt your dbf is out of commission until you fix it or create a new blank dbt. If the memo field becomes corrupt, you had better have a recent backup or you will in all likelihood lose all memos. By having the memos in a separate dbf you only have to restore the dbt file. I have no idea why you get the granular crashes on the memo field, but in any event the separate dbf will eliminate this possible cause of crashes. Also sometimes if you have complicated calculations in a field rule and are getting granular crashes you can replace some of the calculations with a field enter trigger script.

              Russ

              Comment


                #8
                RE: Return of the granular crash-after p-mode

                Thank you so much, you are a world of help...



                Samer N. Gorial

                Comment


                  #9
                  RE: Return of the granular crash-after p-mode

                  Russ & Samer,

                  Thank you both for your help. I'll try the individual memo .dbf. I'll let you know how I make out.

                  Again, thanks so much.

                  Cathy

                  Comment


                    #10
                    RE: Return of the granular crash-after p-mode

                    Russ,

                    Well, I'm trying to take your advice, but now I'm
                    getting no more file handles. I've checked the server
                    -WINNTSystem32config.nt. Those files=25. I can' get
                    on the FAQ's screen where we were told how to set up NT.
                    Thats my server. I can't access my database and our computer people have gone home. I wonder if this has anything to do with removing p-mode?

                    Well-guess I'll wait til tomorrow. Thanks for the help.
                    Cathy

                    Comment


                      #11
                      RE: Return of the granular crash-after p-mode

                      Hello,

                      in my sys config it shows files=255

                      It may have something to do with PMODE ?

                      Mine seems to work fine with or with out PMODE....

                      I would be curious as to how you removed.... remember PMODE MANIPULATES SOME FILES IN ALPHA... so just removing the directory or file will do nothing I would assume?

                      But the only way I can think of to keep truly reverse what PMODE DOES is to reinstall the files PMODE originally changed ...

                      a4v6.net
                      alpha.exe
                      a4.srf


                      I think it is safe to say f you did nothing with these files.... PMODE was not "trul" removed....


                      Good luck....



                      Samer N. Gorial

                      Comment


                        #12
                        RE: Return of the granular crash-after p-mode

                        Cathy,

                        As I understand it, a granular crash is the result on the DOS extender developing a memory conflict. This is usually caused by but is not limited to errors in field rules, calculated fields, custom forms and who knows what else.

                        My experience has been thar P-Mode is more tolorent to these errors, but not immune.

                        If you are experiencing a granular crash, then you may have to redesign your form, field rules, scripts etc..

                        With regards to using Alpha 4 on a network, I believe the proper setup is to have the Alpha 4 executable program on each work station and to have only the data files on the server.
                        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


                          #13
                          RE: Return of the granular crash-after p-mode

                          Ronald & Samer,

                          Thanks for your responses. Our network setup is
                          correct. The removal of p-mode was done by our
                          computer personnel so I'm assuming it was done correctly.

                          From what I read, p-mode was not tested on a network so
                          the effectiveness is questionable. Apparently the memo
                          field I have in my database should be in a separate
                          dbf.

                          The granular crashes occurred both before and after installation of p-mode. So I'll probably have p-mode reinstalled and move the memo's to a child dbf. Wish me luck.

                          Thanks, again
                          Cathy

                          Comment


                            #14
                            RE: Return of the granular crash-after p-mode

                            Cathy
                            We run A4v6.2 on a NT 4 network with about 10 to 12 users continuously pounding on it including memo fields directly in the dbf's. While putting the memo's in a separate dbf (Ira Perlows idea not mine) will help get you up faster in the event of a corrupt memo and can reduce data loss there is no reason why the memo fields won't run properly when part of the dbf. As Ron said its probably a field rule or something else strange. You might try copying the data in the dbf to a new identical dbf and add field rules one at a time until it begins crashing. This might help you find the problem. It is also possible that your dbt is already corrupt in which case you might as well go the separate dbf with a memo route to prevent future hassles.

                            Russ

                            Comment


                              #15
                              RE: Return of the granular crash-after p-mode

                              Russ,

                              Thanks. Trying to pin down the field rules will be a monumental task for me- there are many calculated fields-but I may try that if I can find the time. The separate memo dbf sounds like something I'm able to handle right now.

                              Thanks again for the much welcomed advice.

                              Cathy

                              Comment

                              Working...
                              X