Issues with SourceSafe integration with Sql Server Management Stud

We have a Sql Server Manageent Studio Solution, that on loading gives the
following error:
[ Source Control ]
There appears to be a discrepancy between the solution's source control
information about some project(s) and the information in the project file(s)
.
To resolve this discrepency it will be necessary to check out the project
file(s) and update them. If the check out fails, however, and the solution i
s
closed without saving, you will see this warning again the next time you ope
n
the solution.
[ OK ] [ Help ]
After which it sucessfully checks out one of the projects within the
solution, but makes no changes to it. Is the user (i.e. me) expected to do
something to resolve the issue?
I've tried unbinding source control fro the project that gets checked out,
saved all, rebound, saved all, to no avail.
None of the projects are shared with any other solution files nor are they
shared within VSS.
My normal avenues of finding the cause for these things is coming up blank
-- possibly because the Ctrl+C to copy the text of the error message does no
t
work (presumeably the error dialog is not created with the MessageBox API,
per http://blogs.msdn.com/oldnewthing/a.../29/412577.aspx )Hi Rowland,
Thank you for your posting!
To keep the integrity of newsgroup, we encourage you post only one post in
the newsgroup so that other communities may also benefit from this. We will
reply the post in microsoft.public.vstudio.sourcesafe and follow up your
any questions there.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.

Issues with SourceSafe integration with Sql Server Management

Fair enough -- I only cross posted here, as it was a specific issue with
integration with SSMS.
"Wei Lu [MSFT]" wrote:

> Hi Rowland,
> Thank you for your posting!
> To keep the integrity of newsgroup, we encourage you post only one post in
> the newsgroup so that other communities may also benefit from this. We wil
l
> reply the post in microsoft.public.vstudio.sourcesafe and follow up your
> any questions there.
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>This does seem like an issue that is relevent to SQL Server, and the cross
post seemed appropriate to me.
I think many SQL Server folks would not be looking in
public.vstudio.sourcesafe but rather here or public.sourcesafe.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Rowland Shaw" <Rowland@.newsgroups.nospam> wrote in message
news:5638F572-3306-4A67-9531-4A89EF37CEA0@.microsoft.com...
> Fair enough -- I only cross posted here, as it was a specific issue with
> integration with SSMS.
>
> "Wei Lu [MSFT]" wrote:
>

Issue with Ascii 7 files

Hi All,

I need to generate Ascii 7 bit flat file, based on data in db, using integration services, FTP task. Currently i am generating file with ansi-latin and then using the script task converting it to the ascii 7. File looks to be generated properly. But when the target system reads this, they complain that the file has junk charecters some thing like this. when i open it after generating the file it looks fine to me in DOS also. I dont know what is the target system and what OS is used by them. what cud be the issue for these junk charecters and is it possible that a Ascii 7 file generated by windows doesnt work in other OS? If the method i am doing to generate the ascii 7 is not currect then what is the best method for this?

????H^@.D^@.R^@.|^@.1^@.E^@.N^@.I^@.N^@.A^@.|^@.O^@.|^@.2^@.0^@.0^@.6^@.-^@.0^@.9^@.-^@.1^@.3^@.

PS: earlier i had generated a flat file using data export from Excel & that worked in the target system well. is there any difference in the file encoding generated by excel and integration services?

Please help me!!!!

-vinu

ANSI Latin is extention of ASCII character set. Meaning any proper ASCII text is also valid ANSI Latin text. And ANSI Latin text is either valid ASCII text as well, or contains characters that can't be represented in ASCII at all. So you either don't need any conversion from ANSI Latin -> ASCII, or the lossles conversion is not possible.

I'm not sure what you are doing in the script task, but if you specified the requirements correctly, it is either not needed or not possible :). Anyway, it would be helpful if you include the code.