Thanks to Ira Perlow for this bit of Great wisdom. I had created a complex application and did not realize that my set.rlc was so large (34K). I started getting Crashes when I added Custom Menus. I had checked all the logic and field rules and was going crazy trying to find my mistake(s). Then I found this from Ira. Sure enough, when I changed my set and made the SET.RLC smaller, everything was fine again.(See 4 below) Who woulda thunk?
Wayne
From Ira:
Basically a Granular Crash is due to something that allocates memory that has been allocated to something else. This could be caused by many sources within Alpha, and sometimes due to the Operating System (as in NT clients) acting in an unexpected way to memory allocation.
The cause could be some action that Alpha Form just performed, or something from an earlier point since you started A4. The reasons include things like
1. Bad script (and scripts in Apps) syntax (despite the fact that you say there are no problems) many scripts can work but be syntactically wrong.
2. Bad field rules expressions or overly complex (rename field rules to something else and see if the default one created has any crashes)
3. Something on the layout (typically forms). Could be calculated fields, buttons, menu bars etc. Use a default form to see if problem still exists
4. Overly large fieldrules (RLN for dbf, RLC for sets) + current layout displayed + the application being run. If the size of these 3 files exceed >50k be concerned (50k is not a hard and fixed number, could be 60k, 64k, 48k etc)
5. UDN files seem to corrupt. Delete these and see if the problem repeats (you will lose your default settings, so you will have to reset them).
6. RLC files for sets seem to corrupt to. These can be deleted and will be automatically recreated.
7. Overly complex sets
8. Overly complex posting rules
Hope this can be of some help. Most granular crashes can be avoided with a little work and change of technique.
If you require more extensive help, you can see my web page at http://www.ultranet.com/~csda and contact me for consulting.
Regards,
Ira J. Perlow
Computer Systems Design & Associates
[email protected]
Wayne
From Ira:
Basically a Granular Crash is due to something that allocates memory that has been allocated to something else. This could be caused by many sources within Alpha, and sometimes due to the Operating System (as in NT clients) acting in an unexpected way to memory allocation.
The cause could be some action that Alpha Form just performed, or something from an earlier point since you started A4. The reasons include things like
1. Bad script (and scripts in Apps) syntax (despite the fact that you say there are no problems) many scripts can work but be syntactically wrong.
2. Bad field rules expressions or overly complex (rename field rules to something else and see if the default one created has any crashes)
3. Something on the layout (typically forms). Could be calculated fields, buttons, menu bars etc. Use a default form to see if problem still exists
4. Overly large fieldrules (RLN for dbf, RLC for sets) + current layout displayed + the application being run. If the size of these 3 files exceed >50k be concerned (50k is not a hard and fixed number, could be 60k, 64k, 48k etc)
5. UDN files seem to corrupt. Delete these and see if the problem repeats (you will lose your default settings, so you will have to reset them).
6. RLC files for sets seem to corrupt to. These can be deleted and will be automatically recreated.
7. Overly complex sets
8. Overly complex posting rules
Hope this can be of some help. Most granular crashes can be avoided with a little work and change of technique.
If you require more extensive help, you can see my web page at http://www.ultranet.com/~csda and contact me for consulting.
Regards,
Ira J. Perlow
Computer Systems Design & Associates
[email protected]