Hi,
*hmm* how about inserting into a "test table" (same columns, same data types but no
constraints), and then have a look at the output (I often use this - not very elegant
- method but it works ;-) ). By analyzing the output you should be able to detect
the bug.
kind regards
Frank Schimmelpfennig
PHILIPS Semiconductors Hamburg
ATO-Hamburg WT&IT
"Juchem,
Matthias" To: Frank
Schimmelpfennig/HBG/SC/PHILIPS@EMEA1
<matthias.juchem cc:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
@sap.com> Subject: RE: RE:How to debug
DBPROCs?
17.09.2002 15:51 Classification:
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 17, 2002 3:46 PM
> how about disabling the foreign key constraint and have a
> look at the data your insert statement wants to write?
Wellll, it is not that easy here. I use a view for the inserts and I do not even know
which table the constraint belongs to.
There are several contraints on several tables.
Matthias
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
