You are using the wrong event. Use ListSelection_SelectedIndexChanged event. But, be careful, because this event fires twice on each selection. Once to deselect the old selection and once to select...

What is the sqlserver version of the datasource?

I've gotten that error sometimes on sql server 7.

(fix, http://www.sqlservercentral.com/articles/Bugs/changingcolumn/618/)

I didn't have problems applying 2187. But is wasn't a cluster environment.

You can see the remaing issues >2187 on http://support.microsoft.com/kb/894905/

No clue why the stored procedure gives the error and the adhoc doesn't.

Is the backupserver on the same build as the prod server? There is a cumulative hotfix 2187

http://www.microsoft.com/downloads/details.aspx?familyid=9c9ab140-bdee-44df-b7a3-e6849297754a&displaylang=en

I personally wouldn't risk adding the index. Unless the documentation tells it never can exceed 900 bytes ( odd, when the fields are larger).

Glad to hear that the hotfix solves the problem.

Until I come up with a better one, it is "the problem has fixed itself"

The only reference I've found is

http://support.microsoft.com/kb/945674

Applying the hotfix or

remove custom formatting/appending ""

I agree with Jack, but would switch 3 & 4

SQLServer 2000 is a server application to which various clients can connect.

The permissions on the stored procedure should suffice unless the table is in another database. (crossdatabasechaining option)

I've tried your code. The procedure is created by a db_owner in tempdb.

Errors I've...

Chain of ownership gets broken when you use dynamic sql.

Dumping to a textfile?

3th party tools?

A primary key is unique.

Can you give a short table description?

Hello,

Check if the columns involved in the foreignkey are of the same type/size.

Check if 1side is really unique.

It think there is a quite high limit on the number of foreign...