> >The notes menion "For a full server and client install, make sure to
> >check the item Server for Windows".
> >
> >I was thinking about this. This is what the default was prior to the
> >creation of the client only installer. Should I change the script to
> >have the Server selected by default?
>
> I think so - I fell into the trap myself and I noticed someone else

did today...but leave the 5.6 ODBC driver "by selection only" since it
doesn't work with Dialect 3.

Ok, that's a 5 second change. I'll change it in the next build.

What about replacing the 5.6 driver with the open-source
(Jim's/IBPhoenix/Whatever it's officially called) one? The main problem
I see with it is that it doesn't work with Crystal--which tons of people
use for reporting. The problem with that is that it opens a can of
worms. The ODBC 3.5 core components (I'm assuming it is an ODBC 3.5
driver, but I don't know for sure) setup now uses MDAC which means that
you have to deploy MDAC to use it and I'm not sure I want to get into
dealing with that. I could just install the driver if ODBC 3.5 already
exists, but that doesn't help people who don't have MDAC already.

What are people's thoughts on the ODBC driver?

David R.