> Try dropping the foreign key and see if your error persists.

<...>

> Don't know if any of my suggestions is of any use, but I guess
> they'll at least make you dig a bit further.

I've dug around a bit. It does not seem to be anything to do with the
table itself. I've done a bit of rearranging of the script but it
will take a long time to try significant variations - and it would not
give me much faith even if it did start working.

If suddenly this table started working, perhaps the problem will have
moved to a different table. Or perhaps the problem will reappear with
the next alteration required to the production version. I would need
to create a full test suite and run it everytime I make a change to
the structure - and when problems arise its back to the drawing board
to work out how to stop it.

If I am going to go to that sort of trouble I think I will just write
my own backup routines. It cant be too difficult, and at least I will
know that the data is stored where I can get at it when disaster
strikes.

Thanks for your suggestions.


Geoff Worboys
Telesis Computing