I'd say always use .asp files as includes. That way when script-kiddies try to access your includes the file will have to run through the servers asp engine, thereby hiding your lovely code from prying eyes...<BR>Security man!<BR><BR>sal X
It comes down to a matter of security. But, even that can be overcome -- if you want to use .INC for clarity (I don't know why you don't just put them into an "Includes" folder, but anyway) just tie them to the ASP.DLL in IIS.<BR><BR>That way they are processed, as if, they are ASP files. And your script source is secure.