|
|
Posted by Erland Sommarskog on 02/27/07 16:06
The Man (LeJon7881@gmail.com) writes:
> Thank you very much for your help. I will do that and explain what you
> told me to our vendor. Hopefully they can help with this information.
> The one thing that they have helped me to do is set the time out to
> zero and it seems i still get the same error.
Hm, exactly how did you set that timeout? Usually the command timeout is
set in code only, or not all, which means that only way to change it is
to ship a new binary. But there are other timeouts, that the confused(?)
support staff at PaperVision may have gotten you to fiddle with.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|