>
> In order to check how DBD does the new DBI tricks, so I might
> find time to update DBD::Unify to do alike, I tried to
> install it under Cygwin on my W2k box, but I hit a limit that
> I did not see before:
>
>
> /usr/bin/perl.exe "-MExtUtils::Command::MM" "-e"
> "test_harness(0, 'blib/lib', 'b lib/arch')" t/*.t
> t/01base.........ok t/02simple.......ok 18/19DBI
> connect('DSN=driver=Microsoft Access Driver (*.mdb)
> ;dbq=\\ns01\ns01.S\Work\PRO\LEP\1883
> Sittard-Geleen\VSV.mdb','',...) failed: [Mi crosoft][ODBC
> Driver Manager] Data source name too long (SQL-IM010)(DBD:
> db_logi n/SQLConnect err=-1) at t/02simple.t line 183 Can't
> call method "disconnect" on an undefined value at
> t/02simple.t line 185. t/02simple.......dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED test 19
> Failed 1/19 tests, 94.74% okay
>
>
> I /think/ that that used to work. Is the maximum DSN length
> documented somewhere? I think above example ain't that extreme.
What version are you using? 1.04 I suspect. I think it's the latest
and I think it's a new test that I put in to test DSN= or DRIVER=
opening of the database explicitly, however, it's not smart enough (yet)
to handle a DSN that's already setup that way. If so, and if it's the
only problem, then I believe you are OK. I'll have to fix the test, but
it should only be that.
Jeff
.
