Force Active and Link Spec usage

I worked at a Siebel implementation where we had to deal with a
massive problem caused by a stupid configuration. A very famous
consulting company was doing the project. Naturally they brought some
people who are otherwise good but clueless on some specific siebel
functionality.

During the initial prototyping, a developer put all fields in the
Order Entry and Order line items buscomps to Force Active and LinkSpec
= True. This was an effort to avoid a error from eConfigurator links
(where it pulls fields from a buscomp). He never removed these force
Actives.Project went on and at some point it went to system testing. While
tuning , we found out the massive SQLs which were generated .

We now know the problem . But fixing this will be most difficult. Many
other developers tested their functionality and GUI behaviour assuming
the already Force Active fields. In an Order Entry implementation ,
these buscomps are used heavily and there is no escape other than
basically go thru the whole project and testing each functionality one more time.
Needless to say it was never undertaken , we just made a patch by
removing force Active on some fields we are sure that no one is
using. Imagine that ..For the life of that system , those fields will
be a part of the SQL fired many times during the application session.