Christof:

The text field is the culprit, allright.
I took it out of the SP and it went to completion.
The BOL advises the use of UPDATETEXT for text fields, rather than UPDATE because of possible logging issues.

The client's DB is set for full logging, I keep mine set at simple to keep the files small, hence the difference.

Thanks for the clue!
Bill





>>

Christof:
Thank you for your suggestions.
In my test script, the contents of the email field is the word 'email' or 5 chars.

I had suspected the timeout setting, but both machines are the same (10 minutes), so that one is ruled out.

The SQL profiler sounds like a good place to look.

I'll let you know the outcome.

Bill






>>Hi Bill,

>When I run a stored procedure that takes parameters and updates a table on my machine here, it works fine.

How large is the content of the email field? I've had problems with memo fields in the past, although I can't recall that error message in this case.

I'd check the SQL client configuration. Maybe there's a difference between your machine and the client's one. If that doesn't work, I'd use the ODBC tracing utility to log all ODBC conversation and a network monitor like Ethereal to log the actual network traffice between the ODBC driver and the SQL server. For the server side I'd use SQL Profiler to find out what actually is received.
>>