>Greetings all,
>
>We have an environment that is a mixture of SQL 2000 and 2005. Most of
>my developers are switching over to use SQL Management Studio for both
>SQL 2005 and SQL 2000 (Relational Engine).
>
>We also use Visual Source Safe 6.0 for source code control. We're
>encountering problems with SQL Management Studio re-encoding documents
>to Unicode. We still need to retain backwards compatibility with VSS
>6.0 and with the SQL 2000 tools. When things are in Unicode, we cannot
>use the "Diff" functions in VSS. (There's even some crusty old coders
>(me) who still use windiff!)
>
>I know the best answer is  for us all to move to Team System which
>presumably wouldn't have any problems with Unicode. But that's not
>likely to happen in the foreseeable future.
>
>How can I use the SQL Management Studio but have it leave the encoding
>schemes of the SQL source code files in the original form MS-DOS/Code
>Page 850?
>
>Regards,
>
>Tom

"Tom Huguelet" <tomhug@spammenot_cdw.com> wrote in message
news:mgfaa21q4cnpq8a5fqdm3uusmoi9bgahcq@4ax.com...
> Greetings all,
>
> We have an environment that is a mixture of SQL 2000 and 2005. Most of
> my developers are switching over to use SQL Management Studio for both
> SQL 2005 and SQL 2000 (Relational Engine).
>
> We also use Visual Source Safe 6.0 for source code control. We're
> encountering problems with SQL Management Studio re-encoding documents
> to Unicode. We still need to retain backwards compatibility with VSS
> 6.0 and with the SQL 2000 tools. When things are in Unicode, we cannot
> use the "Diff" functions in VSS. (There's even some crusty old coders
> (me) who still use windiff!)
>
> I know the best answer is  for us all to move to Team System which
> presumably wouldn't have any problems with Unicode. But that's not
> likely to happen in the foreseeable future.
>
> How can I use the SQL Management Studio but have it leave the encoding
> schemes of the SQL source code files in the original form MS-DOS/Code
> Page 850?
>
> Regards,
>
> Tom

>Tom Huguelet (tomhug@spammenot_cdw.com) writes:
>> We have an environment that is a mixture of SQL 2000 and 2005. Most of
>> my developers are switching over to use SQL Management Studio for both
>> SQL 2005 and SQL 2000 (Relational Engine).
>>
>> We also use Visual Source Safe 6.0 for source code control. We're
>> encountering problems with SQL Management Studio re-encoding documents
>> to Unicode. We still need to retain backwards compatibility with VSS
>> 6.0 and with the SQL 2000 tools.
>
>The SQL 2000 tools can read Unicode files.
>
>And as Paul Shapiro said, so can SourceSafe 2005. What I like to add is
>that VSS 2005 is compatible with VSS 6. You probably need VSS 2005 to
>Add and Check in the file, or else it gets listed as binary. But VSS 6
>can still read the database, as the format for the SoruceSafe database
>hasn't changed.
>
>> How can I use the SQL Management Studio but have it leave the encoding
>> schemes of the SQL source code files in the original form MS-DOS/Code
>> Page 850?
>
>CP850? Do you like to hurt yourself? Stay away from that. Or do you need
>compatibility with the 6.5 tools as well?
>
>Any say, as Andrew said, you can use Save With Encoding to resolve this.
>But I guess that if you open a CP850 file in Mgmt Studio, it will think
>it's ANSI, and you will get a mess...