Cascade to null

[Allen Browne]

Anyone have experience with how reliable JET 4 is with cascade-to-null
relations?

I have a scenario where cascade-to-null would be ideal: a child table has 2
parents, like OrderDetails that relate to Orders, and are then also
collected as child records for a client Invoice at the end of the month. If
the invoice is deleted, I want the InvoiceId in OrderDetail to cascade to
null.

Will this work as advertised in a multi-user split database, or are there
bugs/traps here?

 

[Allen Browne]

Okay, I guess the silence means no-one is doing this.
Have enabled it anyway, and the results are very nice.
I just hope it works reliably under stress of real-world use.