> What exactly do you mean by not thread safe
I mean that if you have a program with 2 threads both with Sybase connections you can get a race condition. We've tracked the issue and have seen that a lock has been placed around the offending code in SP127 which is missing in SP125. (I haven't checked SP130)
> are you hitting one of the issues with the multi-thread apps throwing exceptions (CR 761887/764140)?
No idea - what do the CR's relate to ? Do you have a link ?
> What are the issue(s) with the SP130?
> If there is serious issue with SP130 please create an incident with SAP Support.
Haven't looked into the issues with SP130 - we have a lot of test which fail when we upgrade the driver to SP130 which don't fail when we use SP125 and SP127. Its possible that its something we've added to get around bugs in earlier SDK releases (we've been using ADO for a few years so have suffered a lot in the past with the drivers).
One issue we've found is that you can't BCP into a datarow locked table with the last column being a nullable unsigned bigint. Adding a tinyint column to the end of the table fixes it.
> The installer, unfortunately isn't designed to allow extraction of individual components.
Thats a hassle for us developers looking at different versions. I had to uninstall the version I had and then install each verison and then check the code until I found the thread-safe version.
> As for the log - it should be in the %SYBASE%\log directory. If not there something real bad happened to those components - maybe the %SYBASE%\SDK_Suite.log will have information?
Nothing in the logs that I could see. Try with an installation of SP130 installed and then install SP127.