We were making great progress porting SplendidCRM to Sybase Adaptive Server Enterprise 15.0, right up until the Sybase provider failed. 

The hard part is usually converting the SQL scripts to the Sybase format.  It was a bit painful writing SQL functions in Java, but we did it.  And we resigned ourselves into accepting that Sybase does not allow stored procedures to accept a text field as an input.  But it is always frustrating when we have to debug another company's product.

The Sybase ADO.NET driver has a problem when parameters are used through the IDbDataParameter common interface. An Input/Output parameter throws an exception when the Value parameter is accessed after procedure execution.

We have posted a bug on the Sybase site, but we are not optimistic that they will fix the problem any time soon.  Until they fix the bug, we cannot continue.