All of what Adam says, with a couple more examples of what I
think you
are trying to do.
You could include all your <cfinclude...> code each in
an identifiable
block element such as a <div...>. Then using JavaScript
and DHTML
effects you could hide and show different divs based on the
user
interaction with given controls such as buttons. This would
work well
if the content of all the divs are relativly small and
static. If they
are large enough where downloading all of them would have in
impact on
load time or dynamic so that the content displayed in each
section needs
to be up to date at the moment a control is selected this
option will
not work well.
In that case, one will need to had some kind of dynamic
refreshing such
as AJAX or pipe-lines. This adds an dimension to the DHTML
aspects of
your interface to make new request from the server before the
content of
the browser is updated.
Before going into more detail and the hows and whys of each
of these it
would be helpful to know more about your exact requirements
and comfort
level with various technologies and techniques.
As Adam concluded there are many ways to solve this type of
problem.
AdChoices