note
mpeppler
I don't know all that much about the issues with DBD::Sybase & MS-SQL, but I can try to help.<p>
The most likely problem is that you are for some reason opening more than one connection. This can happen if DBD::Sybase thinks that the connection is still active when prepare() is called. You can set the syb_no_child_con connection attribute to TRUE and this will inhibit multiple connections for simultaneous statement handles.<p>
You can also enable the DBI->trace() to see what really happens under the covers.<p>
Michael
559715
560058