I am not sure I understand what you're asking here... (the absence of some line breaks here and there didn't really help... ;) )
Anyway, the way includes work is like this: before the code in a file is parsed, all include files referenced in the main page (and any other includes that those include files include in turn) are collected and put into one long file which is then executed. So, it doesn't really mater what you put where in an include.
I am not aware of a limit on include files, or the maximum number of them for reasonable performance. However, you can easily have like 10 includes in your file, although I personally think that's way too much....
However, there are a few rules you should stick to to make your fellow developers and design time tools like Dreamweaver happy:
1. Don't put partial tags in an include.
So, don't have an include that has just a bunch of <tr> tags and that assumes it'll be included in a file that sets up the outer <table> tag. Includes are about reuse, and partial tags make that very difficult. However, inside the include file, you can use whatever HTML or ASP code you like.
2. Don't get carried away with includes. I have seen sites where partial content was moved to an include while it could have been placed directly in the page. If you're not going to reuse it anywhere else, place it in the page directly.
3. Depending on your preferences, you can either put surrounding divs in the main page, or in the include. E.g.:
<div id="Menu">
' Include here
</div>
or:
' Include here
where the include file then looks like this:
<div id="Menu">
Content
</div>
I prefer the first, but that's up to you.
Does this help?
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to:
5 Years by
Björk (Track 6 from the album:
Homogenic)
What's This?