You can put a check constraint on the shell field to prevent its use.
Several of the Emerald functions will display a msgbox of the message
to the user is the message = 50000 And Severity = 17. This allows
business rules at the SQL level. Of course, I wouldn't recommend
modifying these unless you really understand checks and constraints
with SQL Server.
I built one for a customer a while back that checked for the
default incident type, and would refuse to save it (forcing
the users to actually pick an incident type, and not just leave
it on the default).
Dale E. Reed Jr. Emerald and RadiusNT/X__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart