Just run into a "feature" of XE.  The <Del> key remains active in a
dbEdit component even when the dataset is in browse mode. I only noticed
by accident as I've been porting a working application from D2006 (don't
ask) and found a difference in the behaviour.  It means an end user
could delete the content in the dbEdit component and trigger an error
about the dataset not being in edit mode.

If someone has insight into this situation, I would appreciate comments.

I've done a work-around by setting all the components ReadOnly property
based upon the current dataset condition... seems like it should be
unnecessary tho'

JonD