Found it. (thanks Sharon.) I left some commented out code in my dw control's dberror
event. I sure wish PB wasn't so finicky about those comments!
BTW,
I've got some itemfocuschanged code that searches for duplicate entries during data
entry. If it finds a duplicate, it pops up a dialog that asks the user whether they
want to move to the original, or modify the current one. It's a little more graceful
than the dbms-speak provided by the regular error dialogs.
Marvin Young
Washington State Department of Fish and Wildlife
[EMAIL PROTECTED]
(360) 902-2508
>>> Marvin Young <[EMAIL PROTECTED]> 8:01:34 AM 11/19/1999 >>>
What's the "standard" way to deal with those duplicate database error messages?
I've tried the ib_error_reported toggle. But it doesn't affect errors coming from
pfc_save.
Is there some sort of tweak I can make to the error service to make it REPLACE db
error messages instead of DUPLICATING them? Did I turn something off by mistake?
Thanks for your help,
Marvin Young
[EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
!
!
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
- PFCSIG Duplicate db Error Messages Marvin Young
- Marvin Young
