> Looks like applying SQL Server SP3 did the trick. It was > installed previously, but the SQL Server was *re*installed, > and the SP was not applied.
Oh yeah, I forgot to mention that. That fixes a lot of problems, such as using named instances. > MDAC *before* the SP was installed showed 2.8 - which is most > current at the time. Perhaps something else in the SP fixed a > connection error?! MDAC doesn't really have anything to do with SQL Server itself, as far as I can tell. While SQL Server requires a certain MDAC version level to accept ODBC or OLEDB connections, the version of MDAC on your SQL Server doesn't affect connections from other machines. In any case, when you select "Microsoft SQL Server" within CF Administrator, that uses a "pure Java" JDBC driver which also doesn't use MDAC, as far as I can tell. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201598 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
