If you make the cascade delete option restrict the child delete it
gets tested if they try to do it. This seems to me to be a better way
to avoid the performance hit. Controlling the delete button as others
have noted seems more friendly based on a hot field. Disable on the
button will deal with the popup browse menu too. A use just scrolling
does not need to know if there is a cascade delete issue. If extended
to the limit you would not be able look at the record if it couldn't
be deleted.
The flicker problem I have solved by just wring my own hide and
disable commands that check to see if the desired state is the current
state. If you want to play with buttons as you scroll it helps to do
as Paul Noted. I have an app with about 10 of these I manage and the
flicker is a killer if you don't manage the state of the buttons. If
you use hide instead of disable you also need to disable too if it is
in a browse popup menu. You can't hide popup menu items once they are
added but disable works. Popup menus are directly tied to the buttons
they mimic.
On 29 Mar 2008 10:58:59 -0500, Kent Baldwin <kentbald@[EMAIL PROTECTED]
>
wrote:
>I test for child files before allowing delete.
---------------------------------------
Paul Blais - Hayes, Virginia
