Re: Designer 2000 Questions

From: Ian Sparkes <isparkes_at_analysts.com>
Date: 1997/01/22
Message-ID: <01bc0899$b600b750$8415f5cc_at_primenet>#1/1


On using CG_REF_CODES...

IMHO... The is a fine dividing line when to use this and when to use separate tables, The explanation I give to my engineers is

If the data is either static or the changing it will require application changes, then it is a good candidate for CG_REF_CODES. If on the other hand data changes can be made that effect the application the use a separate table.

An example if this would be an application that calculates state tax. Let us assume that in V1 of the App on CA, TX and FL were supported. If in V2 you wanted to add NY, it would do you no good to add NY to a "State" table as you would still have to write the code to calc. the tax. You should look at CG_REF_CODES as part of the application with all the version control issues associated.

The other issue is that creating multiple tables/forms to support RI lookup that do not meet the above criteria is some simple with the forms generators that the effort involved is minimal once you figure out how to do it. Typically I would expect an application to include both methods.

As a final note, I really dislike the idea of creating a multi-use lookup table of your own, this makes using declarative RI and generated forms real difficult (re: Costly and time consuming). Received on Wed Jan 22 1997 - 00:00:00 CET

Original text of this message