> It's Access, my guess is that as long as I can see the .mdb
> files I'm good to go. There are guys out there that are crazy
> about Access! Maybe they are just crazy...
>
> >From the ASP:
>
> Set Conn = Server.CreateObject("ADODB.Connection")
>
> I'm assuming there is an ADO driver installed and I would
> think there may be an ODBC as well. If not I can snag the ADO
> driver from xmlproj.com
>
> What advantages does the ODBC have over the ADO, aside from
> Jeff Urlwin being a pretty nice guy!
Well, shucks. Thanks.
Honestly, I don't know the "technical" differences between ADO and ODBC
(in terms of behavior, rather than "API"). I do know that I've spent a
*LOT* of time trying to get stored procs, multiple result sets and other
strange things working as well as I reasonably can with DBD::ODBC,
especially using SQL Server. I suspect since these tasks are relatively
rare and there are a lot of test cases that DBD::ADO may not be as good
in that area -- just because of lack of need, rather than anything else.
I spent the time because users came to me and said "I need this to
work".
That said, ADO could be a lot better in those areas, I just don't know.
My guess is that your mileage may vary. It will depend upon what you
are doing and what drivers you are using. Access is relatively
straight-forward and should be supported well by both, but there are
quirks with Access as you know.
I'd also _suspect_ that more effort is being put into the ADO drivers
themselves, rather than the ODBC drivers, but you never know, do you?
So -- good luck either way.
Jeff
