| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3984.1 | | DSSDEV::RICE | | Wed Feb 19 1997 08:42 | 5 |
| I'm not sure what it is you're looking for us to tell you; Yes, this should
work just fine and does for everyone else? Maybe you need to look into those
undefined symbols errors from the linker.
-Tim
|
| 3984.2 | ideas... | CSC32::C_BENNETT | | Wed Feb 19 1997 12:06 | 36 |
| Hello,
The PROC_ESCAPE_ERR error is a catch all error signaled by the DECforms
condition handler - this is not necessarily a DECforms issue.
FORMS
Errors
PROC_ESCAPE_ERROR
request terminated due to severe error in procedural escape
routine
Explanation: An escape routine being executed as part of the
current request signalled a fatal error. The request has been
terminated.
User Action: Examine the trace log and determine what error was
issued during processing of the escape routine. Correct the
error signaled in the trace file.
What I would reccomend is compile, link and run with the /DEB. Set
a break in the ESCAPE ROUTINE and step thru the code in an attempt
to understand the offending command which causes the exception to
be raised.
LIB$ESTABLISH in the ESCAPE ROUTINE could also be used to superceed
DECforms condition handler and give additional information.
The trace file may also have information about the primary cause of the
error. The PROC_ESC_ERROR secondary error only says that an exception
was raised - you need to dig in and correct the primary cause of the
error.
This error for example could be an untraped/unsignled SQL exception -
not necessarily a DECforms error...
|
| 3984.3 | thanks | KTOV12::SUZUKI | sophisticated typist | Wed Feb 19 1997 20:53 | 8 |
|
I'd like to know my porting(compile,link) was right or not.
Nobody say it's wrong, so it must be right.
So, I'll fix all UNDFSYMS.
Thank you.
Naoko
|
| 3984.4 | ;-< | CSC32::C_BENNETT | | Thu Feb 20 1997 08:43 | 14 |
| .3 Nobody say it's wrong, so it must be right.
If it runs it must be right sometimes, if it fails,
something must be wrong sometimes.
2.1B version along with the ALPCMAR04_061
patch would bring you up to the latest release - I would
reccomend that. I would translate under 2.1B also.
The PROC_ESC_ERROR indicates an error has occured
in the ESCAPE ROUTINE. What you need to do is find
the error and fix it. The trace facility may give you
secondary errors which could actually be primary cause
of the PROC_ESC_ERROR.
|
| 3984.5 | | KTOV12::SUZUKI | sophisticated typist | Fri Feb 21 1997 06:34 | 24 |
| > If it runs it must be right sometimes, if it fails,
> something must be wrong sometimes.
Now I fixed all LINK-W-UDFSYM, so the FORMS-E-PROC_ESCAPE_ERR
disappeared, and Another one RDMS-E-CSETBADASSIGN come.
So, maybe my forms porting was right.
> 2.1B version along with the ALPCMAR04_061
> patch would bring you up to the latest release - I would
> reccomend that. I would translate under 2.1B also.
Than you. I try to find Japanese-2.1B.
> The PROC_ESC_ERROR indicates an error has occured
> in the ESCAPE ROUTINE. What you need to do is find
> the error and fix it. The trace facility may give you
> secondary errors which could actually be primary cause
> of the PROC_ESC_ERROR.
Yes, you are right. But, I'm in a hurry.I must finish porting
this application to AXP in this month for my customer.
Thanks for your advices. I'll try to do so.
Naoko
|