Re: MSSQL + FreeTDS and No SQL Errors Returned

We have been using Openlink while in development and so far it has worked flawlessly, at this point we plan to purchase and use it in production. We also are stuck with MSSQL but I've found it to work just fine so far. Currently we only call stored procs, leaving the SQL to the database folks. Performance is quite good this way as the SQL stays compiled on the DB Server between queries. We plan to move up to the latest version on the new dev box as Openlink now supports ODBC 3.5 (my version # may be off, Andrew?) I've no complaints so far with Openlink and our developers seem to be happy with it, though I think sometimes they would just as soon write their own SQL rather than wait on the DB folks to deliver changes ;^) DAve. on 8/2/00 4:03 AM, Sanders, Nicholas at SandersN@logica.com wrote: > What would you suggest then? And don't say MySQL because I'm stuck with > M$SQL. Are the sybase drivers any better and what about ODBC? > > Can I look at this core dump to give me idea about what is going wrong? > > Nick >