Hoe to get Encrypted Password value varbinary field

I just converted from SQL 7 to SQL 2000 but have one issue.
My login table contains a password field that is a varbinary type. I
encrypted the value by using the encrypt('password') when inserting users
into this table.
How can I see the actual value of the password field. Is there a way to
decrypt?
For some reason, all the users passwords don't work. If I redo each one, it
works but there are too many to redo manually."yodakt" <dev1on11@.gmail.com> wrote in message
news:6E45D35E-970E-4656-AECF-B192BD1035D7@.microsoft.com...
>I just converted from SQL 7 to SQL 2000 but have one issue.
> My login table contains a password field that is a varbinary type. I
> encrypted the value by using the encrypt('password') when inserting users
> into this table.
> How can I see the actual value of the password field. Is there a way to
> decrypt?
> For some reason, all the users passwords don't work. If I redo each one,
> it
> works but there are too many to redo manually.
Try this:
SELECT CAST(myPassword AS NVARCHAR(100))
FROM myTable
Where myPassword is the VARBINARY column containing the passwords.

hiding "Change Credential" link

Is there any way to hide "Change Credential" link comes in browser?

I cannot change the credential type, It will be "Prompt" only as i am passing connection string and Credentials via URL.

You can hide the entire prompt area by specifying rc:Parameters=false in the url. Note that this will hide both the data source and the parameter prompts. There is no way to hide only the data source prompts via url access. If you use the ReportViewer webforms control, then you can control the parameter and data source prompts independently.|||

thanks Brian.

I am able to hide "Change Credential" link using mshtml object. mshtml object, has property called "document", using that you can get all the controls on the pages. Top three rows i am hiding using that.

Hope microsoft will not change the structure of HTML page, generates by Report Server.

|||What you are doing may work in the current version, but it is not a supported mechanism for changing the viewer. The html structure may change in a future version or service pack.