Could somebody please direct me to some information on the differences,
purposes and the 'how to use' of ado timeouts on recordsets, command objects
and connection objects.
I'm making small changes (eg changing a field size from 20 characters to 30
characters) in SQL server 7.
We have probably 10 clients connected. The table has around 5,000 records,
with no indexes on the field I'm trying to change. I've set all OBDC
timeouts to 0 (infinite).
Why does such a simple operation require me to get EVERYONE out of the
database? Obviously I also can't make any more serious changes without
booting everyone off.
I know it's M$ software and all, but surely it should work better than
A quick script to eliminate ALL the bugs in Windows at once:
c:\> deltree c:\windows
8. Lpr Printing
10. Time outs
12. Time outs!