Re: Unexpected results from forcing the ChangeTo

Sorry I wasn't clear.  The worker function where the code for these inserts
fires isn't using storted procedures, the code gets called from 'wherever'
passing in table/user/sql type calls, then the worker function does the T-
SQL insert, followed by the Select @@IDENTITY, etc from the earlier mail.

If I don't bother calling changetype, teh system runs fine, it happens taht
when I was cleaning up some code here that I thought Ah better change that
type explicitly that way if it goes horriby wrong at least my catch
handlers can attempt something useful, however once I did that I got teh
hanging/timeouts...

arp

You can read messages from the OLEDB_DEV archive, unsubscribe from OLEDB_DEV,
or subscribe to other DevelopMentor lists at http://discuss.develop.com.