Getting a GPF in DWB when reading/saving record (OpenInsight Specific)
At 12 DEC 2001 12:40:10PM Steve Carlson wrote:
I have a Form named "MARKETING_PRACTICES_TO_REPORT" with a
button's name "SORT_SELECT_BUTTON".
So I have a click event named:
"TEST_APP*CLICK*MARKETING_PRACTICES_TO_REPORT.SORT_SELECT_BUTTON"
in "SYSREPOSEVENTS".
When I run the form and press the button I get thrown into Debug.
If I try to edit the event in the system editor, I get an "application error" box saying "DWB caused a General Protection Fault in module USER.EXE at 0001:43AD. Choose close. DWB will Close"
What might be the problem??? The "SYSREPOSEVENTS" file does not have any Group format errors through LH verify..
Thanks..
Steve Carlson
At 13 DEC 2001 03:22AM Oystein Reigem wrote:
Steve,
Why do you edit the event with the System Editor? What happens if you use Form Designer?
- Oystein -
At 13 DEC 2001 08:03AM Steve Carlson wrote:
] Why do you edit the event with the System Editor? What happens if you use Form Designer?
Oystein, I can edit it fine in the Form Designer. the code is only a
few lines long and is an exact copy of a button in another form. I
compile the form fine… but when I press the button I keep getting
thrown into debug and it acts like it can't find the compiled "event"
attached to the button. So I try going thru system editor thinking the
system can't recognized the event, and sure enough I get the GPF error
message.. It just seems the system doesn't want to read the event code from the system…Form designer works ok…. Is there a limit to
the total length of the event name???
Steve C.
At 13 DEC 2001 10:09AM Oystein Reigem wrote:
Steve,
]] Why do you edit the event with the System Editor? What happens if you use Form Designer?
] Oystein, I can edit it fine in the Form Designer. the code is only a few lines long and is an exact copy of a button in another form.
The button is a copy of a button from a different form? Could that be significant?
What does System Monitor say?
Or is it just the code (source) that was copied?
] I compile the form fine… but when I press the button I keep getting thrown into debug and it acts like it can't find the compiled "event" attached to the button. So I try going thru system editor thinking the system can't recognized the event, and sure enough I get the GPF error message..
I did a search on DWB and GPF and found there was a bug once with similar symptoms - in OI 3.2 I think. Something with the System Editor's File | Open Stored Procedure crashing when the volume of keys (procedure names) to display in the Open dialog's list box exceeded 64K. But firstly you don't open stored procedures but records, and secondly your version of OI is much newer than 3.2. Or???
] It just seems the system doesn't want to read the event code from the system…Form designer works ok…. Is there a limit to the total length of the event name???
I'm sure I must have longer names than yours in my app.
Stupid question: Could it be something wrong with the code itself? The source, I mean. What does it do? What happens if you comment it out?
And can't you just delete the control and recreate the handlers from scratch?
- Oystein -
At 13 DEC 2001 10:52AM Steve Carlson wrote:
]]] Why do you edit the event with the System Editor? What happens if ]]]you use Form Designer?
]] Oystein, I can edit it fine in the Form Designer. the code is only ]]a few lines long and is an exact copy of a button in another form.
]The button is a copy of a button from a different form? Could that be ]significant?
No, the "button" isn't a copy, I just copied the source code of the
script and pasted it in the new form's button click event.
]What does System Monitor say?
I get an "application error" box saying "DWB caused a
General Protection Fault in module USER.EXE at 0001:43AD. Choose close. DWB will Close"
]Or is it just the code (source) that was copied?
Yes, just the source code was copied.
]] I compile the form fine… but when I press the button I keep ]]getting thrown into debug and it acts like it can't find the ]]compiled "event" attached to the button. So I try going thru system ]]editor thinking the system can't recognized the event, and sure ]]enough I get the GPF error message..
]I did a search on DWB and GPF and found there was a bug once with ]similar symptoms - in OI 3.2 I think. Something with the System ]Editor's File | Open Stored Procedure crashing when the volume of
]keys (procedure names) to display in the Open dialog's list box ]exceeded 64K. But firstly you don't open stored procedures but ]records, and secondly your version of OI is much newer than 3.2. ]Or???
Yep OI version 3.7.5
]] It just seems the system doesn't want to read the event code from ]]the system…Form designer works ok…. Is there a limit to the ]]total length of the event name???
]I'm sure I must have longer names than yours in my app.
]Stupid question: Could it be something wrong with the code itself? ]The source, I mean. What does it do? What happens if you comment it ]out?
The source code is:
DECLARE SUBROUTINE PRINT_QEVENTS
CALL PRINT_QEVENTS(CtrlEntID,CtrlClassID)
RETURN 0
If I comment it out I still get the same results.
]And can't you just delete the control and recreate the handlers from scratch?
I have deleted the code and re-entered it with no difference.
Steve C.
At 13 DEC 2001 01:36PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Steve,
There is a 60-character limit on event keys in the system… and when I say event keys I mean 60 characters INCLUDING the '$$$' stuff the system tags on the front when it attempts to execute it, so you're actually limited to less than this amount.
The key you specify is way too near this limit …
This has been there since OI2.0 beta and I imagine it's what's causing your problem.
World leaders in all things RevSoft
At 13 DEC 2001 03:34PM Steve Carlson wrote:
Ok… maybe this will be fixed with OI 32. I guess I'll just rename
the Form to a shorter name..
Thanks… I'm glad it's not just me.
Steve C.
At 14 DEC 2001 03:42AM Oystein Reigem wrote:
Steve,
Sprezzatura's right. I tried with a form and a button with long names, and got the same symptoms as you. When the Debugger said "Error loading program etc" I could clearly see the name had been chopped at 60 characters (60 including $$$). If the system truncates the name of the event before it tries to execute it, the message makes perfect sense.
I really was sure my apps contained events with names as long as yours, but it seems my longest was 57 (60 including $$$). A close shave indeed. I think what's saved me is the use of quickevents.
- Oystein -