Frames are rarely a good idea.

To better answer your question, we need to know WHY you chose to use Frames
in the first place.

If you were using it to organize your page layout, odds are that you'd be
better off using CSS.

If you were using it to maintain common components, odds are that you'd be
better off using webControls.

-Darrel

Thank you Darrel. To give you more details, my front end may look like msdn
site not same just to give you some idea... on left frame tree control on
right side 4 frames which can be collapse and expand. On first frame I have
controls like list box and buttons, second frame has also same controls but
list box will populate base on selection on first frame, third frame will
have all dynamic controls (list, text, dropdown,cal.) generation. and forth
frame I am planning to put Grid View which I use now OWC (PivotTable)
control. When button clicked on first frame (Run Query) I want to read data
from all the frames build Query Request (may be xml) get the data from
database and show data on forth frame's Grid View.
Frames works fine now because when user selects any thing on first frame my
whole page doesn't do post back (for users they don't like flicker on page).
Even there are lots of Java scripts but some how it's easy now working with
different frames.
There are also lot of data stored in session as you see in the third frame I
have dynamic controls and data all saved in session.
Tree control on left should also expand and collapse to left.
User wants frames to collapse because once they run the query they want full
page to see data (Grid View) on forth frame. Hope you got the idea.
I need help to get correct direction what I should use because I am starting
again in .net 2.0 and want to use if there are any better framework for my
development.

Thanks a lot - Ashok

"darrel" wrote:

I wouldn't use frames to just get rid of the 'flicker'. Loading pages on the
internet is how the web pretty much works. People are used to it. It's not a
'bug' to fix.

So, instead of frames, I'd use web controls. One for your menu, a handful
for your content, etc.

Getting Javascript to behave across frames is a chore. Another reason to
drop the frames.

This might be a reason to use frames. You might also be able to use
viewstates instead, though.

If you are ambitious, check out using usercontrols for your compoents, and
CSS + AJAX for your interface. AJAX will give you the layout control you are
looking and allow you to not have to do full page reloads without having to
deal with frames.

-Darrel