Well, it appears this only happens in my Database projects. I have a VS 2008
database project that contains a number of SQL stored procedures. If I select
Add a New Item option and pick SQL script, or stored procedure as the file,
it creates a new file just fine. But when I select File-->Advanced Save it
shows the code page as Unicode (UTF-8 with signature) - Codepage 65001. If I
forget to save with a different encoding and then try to compile all my
stored procedures through a VB script, the new one will fail because of the
encoding bytes at the beginning of the file.

I'm not sure why this only happens with my database project files. I tried
this with a C++ project and any new files are created using codepage 1252,
Western European (Windows) which is what I really want.

I did not see any way to change this default behavior for database project
files so that's why I was posting this in case there was a way that I'm not
aware of.

Thanks.

-Dave