>> I have a user defined table with a variety of information with a I
have a user defined table [sic] with a variety of information with a
variety of meanings. Each record [sic] has an identifying key
[redundancy] from another table associated with it to tell me what the
data means. <<
That first paragraph is total nonsense:
1) SQL uses rows and not records -- major difference.
2) Users do not define tables; they use them. DBAs declare tables in
3) Does the concept of a "non-identifying key" make sense?
4) A table is a set of one kind of thing; by definition, it cannot
contain "a variety of information"; it contains "one and only one kind
of information" -- a werid phrase, but closer to the definition.
5) The scalar values in the columns of each row are drawn from **one and
only one** domain (see First Normal Form and the definition of a
relation); they cannot ever have
"a variety of meanings".
There are columns in SQL, not fields -- major difference.>> UDF stands for user defined field [sic]. <<
Even if your request made any sense, you did not post DDL, so that
people do not have to guess what the keys, constraints, Declarative
Referential Integrity, datatypes, etc. in your schema are.
You need to get a book on relational design and start over. I am sure
you can kludge together an unmaintainable nightmare and do a million
monster joins to obtain unverifiable results without an data integrity
in a fantastic amount of time. But please don't; you will ruin your
*** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
Don't just participate in USENET...get rewarded for it!