by I currently am developing an application that relies one one main table
with about seven subtables in a one to many relationship with the main
table. Each subtable, for various reasons has what I describe as a
default value (better described as a default tuple), so on the data entry
form, if the user does not enter information for that field, the default
value is used. The subtables are defined by an Autoincrementing field,
and a user changeable 'Name' field. A tuple is designated as being the
default it its autoincr. field has a value of 1.
Now, I also have a query builder that supports the SQL DELETE command, and
it is possible that the user can delete the default tuple in a table,
causing all sorts of problems. Is there a way to prevent DELETE queries
from removing this tuple? For example if the user enters DELETE * FROM
[Composers] WHERE blah.., should I parse this to DELETE * FROM (SELECT
* FROM Composers WHERE Key>1) WHERE blah..?
Is this on the right track, or is there a simpler way of doing this?
Thank you,
KEvin Brill
___
*******************************************************************
* Kevin Brill University of Florida *
*-----------------------------------------------------------------*
* "...can you believe Jorge Orta lost that ball in the sun? How *
* can a guy who was raised in Mexico lose a ball in the sun?" *
* - Harry Caray (God bless) *
*******************************************************************