Hi Gene,
first of all vfp creates vfp code in the dbc, so everything
the ri code does can be seen and/or modified the way you'd
like it. This also regards the order of tests. Other third party
ri code builders may be a better choice, as they normally
create code better understandable. TaxRI and AMRI are
two I know of. AMRI eg creates a public var _RI_Message
which makes it easy to react to trigger errors.
Quote:
1) If a column constraint is violated (error 1582)
Try Sys(2018) or see what AERROR() stores in the elements
|
of the array created.
Quote:
2) Is it possible to find out which trigger failed?
definately with AERROR(). See what the helps says
|
on element 5. Normally that is NULL, but with error
1539 this has info about the trigger type.
Quote:
3) Is there any guarantee of which order the constraints
are checked / the errors are thrown?
See my initial remarks. I think vfp first checks the
|
full record (all FKs) in their field order, then it recurses
for cascades. But I'm not that familiar with vfp native RI
code. I only know there were an error with multiple
cascades not rolling back deletes when stepping to some
restrict. As you use vfp6 you may still have these errors.
I'd recommend to use some other RI builder.
Bye, Olaf.