Thanks Mark You've kind of answered my question indirectly :-)
The Developer Tool for example, which we only use in Development ( not clustered ) to clean out user records as we're working, deletes a user and any objects it holds relationships with. If the cache keeps hold of the changes as the script runs, and we've switched that off, then that would explain why it thinks there are constraints in place when it tries to cascade delete. I tried removing the problem relationship manually but it was still grumbling at me. All this is probably not an issue at the moment but I'll keep it in mind if / when we need to do any clean up work. Cheers, James -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
