On Jul 25, 2006, at 9:24 PM, Mike Kienenberger wrote:
In my testing, I submit a web request that creates a new object, submit a web request which creates another set of new objects and assign it to relationships with my first new object, then submit a web request which deletes the set of new objects.
Mike, just a guess. Looks like the reverse relationship of FeeCycleType.feeCycleList doesn't have nullify delete rule. So you can either set such delete rule, or manually break relationship after delete. This explanation looks too simple, but all the symptoms point to it.
Andrus
