Code Validation in CASE-generated CDE Application

We are using CASE 5.1 to develop an Oracle Forms 4.013 application. The issue of handling validation codes has come up and we are having a debate within the project team. We would like input on how other sites are handling this situation.

We all agree that small,static code sets like "gender code (M,F)" should be implemented in the database as check constraints.

The disagreement occurs over situations where we have a code and it's name/description. One group thinks that each of these should be implemented as a separate table with a CASE-generated form to maintain the data. The other group thinks that codes of this type should be centralized in a generic codes table with a single generic codes maintenance form.

The criteria for these code types are:

1.) No attributes other than the key and a name or description.
2.) More than a few (>6) discrete values.
3.) Subject to routine maintenance (inserts,deletes).

The estimate of the number of data elements that fall into this category range from 50 to several hundred.

Is anyone out there using either of these approaches to deal with this situation? Is there another approach that we're not considering?

Please let us know what you think.
-Thanks. Received on Thu Dec 01 1994 - 23:20:10 CET