[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE still makes mysterious distinction between RETURN ERROR CH-Error versus UNDO THRO

Status
Not open for further replies.
S

ske

Guest
> But despite all the similarity between the two, when it comes to the agent > log one makes "noise" as the error is being transmitted to the .Net openclient and one does not. Perhaps the best "fix" would be for the AppServer to stop logging an error when an AppError is thrown to the client in those cases where the AppError does not contain any other information than the RETURN-VALUE. That would make AppError and RETURN ERROR more fully equivalent and interchangeable.

Continue reading...
 
Status
Not open for further replies.

Similar threads

D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE still makes mysterious distinction between RETURN ERROR CH-Error versus UNDO THRO
Replies
0
Views
398
dbeavon
D
D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE still makes mysterious distinction between RETURN ERROR CH-Error versus UNDO THRO
Replies
0
Views
393
dbeavon
D
D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE still makes mysterious distinction between RETURN ERROR CH-Error versus UNDO THRO
Replies
0
Views
429
dbeavon
D
D
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE still makes mysterious distinction between RETURN ERROR CH-Error versus UNDO THRO
Replies
0
Views
395
dbeavon
D
L
  • Locked
[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE still makes mysterious distinction between RETURN ERROR CH-Error versus UNDO THRO
Replies
0
Views
409
Laura Stern
L
Top