Non-Deletable Master Preventing Delete of Detail [message #326775] |
Thu, 12 June 2008 09:56  |
annagel
Messages: 220 Registered: April 2006
|
Senior Member |
|
|
I am working on a new form which has a psuedo master block which is actually just a view which gives a distinct listing of person names from a person actions table. The person id value from this master view is used to populate a detail block which contains the actual actions. The actions themselves are sometimes deletable, other times not deletable and this is controlled by a WHEN-NEW-RECORD-INSTANCE trigger.
I had set the update, delete, insert properties for the master block to no as it is just a summarizing view and those actions don't really make sense for it. It appears doing this is preventing me from deleting detail records when I aught to be able to. I have gotten rid of the trigger on the detail block to make sure that is not causing my problem, and then tried turning the delete on for the master block. Turning on delete did then re-enable delete for the detail block.
This behavior does not really make sense to me, I should be able to set the deletion for the master relationship to non-isolation and get the same type of result, but in that case the button will still be enabled you would just always get an error if you pressed it.
Any ideas on why the behavior is this way? Or ways to get around it?
|
|
|
|