>
> On Tue, Oct 22, 2002 at 10:24:39AM -0400, Jeff Urlwin wrote:
> >
> > Sorry -- brain problem, this morning. I was going to say, how about MS
> > Query (not analyzer, but the query that comes with MS office which just
> > queries the db), then I looked further to see you were on
> Linux....can you
> > give us a little more about your configuration? I can guess
> that you may be
> > using one of the following:
> > - 1) using DBI, DBD::Proxy or and MS ODBC drivers on the
> SQL Server side.
> > - 2) using DBD::ODBC and EasySoft OOB or some other bridge
> > - 3) using DBD::ODBC and something like FreeTDS
>
> It appears to be DBD::ODBC and FreeTDS. At least, the DSN name shown in
> ODBCConfig which matches my code says FreeTDS alongside.
> (TBPH it's been a long time since i set it all up and am a bit hazy on
> what i did.)
If you are using FreeTDS, then it's irrelavent what version of the ODBC
driver is running on the server side. It's probably just a client side
problem.
What I suggest is:
- determining which (if any) ODBC driver manager (i.e. unixODBC) you are
using. Try using isql or the driver manager's sql interface to see if you
have the same problem. It's likely you do. In which case it's FreeTDS or
the driver manager causing it. If you built DBD::ODBC directly against
FreeTDS, then, check which version. I ran 0.53 and had issues. I haven't
tested with 0.60 yet, but there have evidently been major improvements to
the ODBC portion. That said, you are in a grey area for me as I don't have
a lot of time to muck with that configuration. You might also try
DBD::Sybase using FreeTDS...as I suspect that DBD::Sybase using FreeTDS
directly may be more stable than DBD::ODBC using FreeTDS's ODBC library,
then FreeTDS...just from my experimenting with FreeTDS 0.53...
Regards,
Jeff
