Sergey,

I wasn't sure that SPT would work because of the large binary string that had lots of "weird" characters in it. I found out that Rick Strahl's wwSQL.InsertBinaryField() method uses SPT and seems to solve the problem for me. I have been away from UniversalThread for awhile, but it is good to see that you are still here saving the day! It is greatly appreciated.

Kevin


*********************
For alternative way to work with blob fields in SQL Server , see mskb #258038 and mskb #272338
>
>Error: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid locator de-referenced.
>
>I see a KB article #245714 that says: "You cannot insert more than 250 KB of data in a SQL Server 7.0 or SQL Server 2000 Image field from Visual FoxPro".
>
>Now I seem to be able to insert large data files using remote views all the time, but this error has cropped up lately and I found the above KB article. In the past when I got this error, I just recreated the remote view via code and everything worked. I have a new user where I am having trouble transferring the VFP data to SQL*Server using a remote view. Has anyone seen this issue before and found any solutions? (Note: MS's 1st KB article solution doesn't make any sense --> do they mean breaking up the updates in non-image and image updates?)


--------------------------------------------------------------------------------