We are migrating from an ancient MX7 on MS Server 2008 to MS Server 2016 (IIS10) and CF2016. Lingering problems exist when testing the new setup. Why Access? That is a common question, to be sure. We are beginning the learning curve for SQL Express 2016. (Just two old self-taught CF dudes)
We were able to successfully install MS Access drivers with HTXX drivers via the CF Admin DataSource page. (HXTT MS Access JDBC Drivers) Other forum postings on Access solutions were echoed by Charlie in forum postings. I will post those settings to the original thread.
Testing the new configuration indicates that we are not handshaking with our data connectors as only a couple static pages resolve. Using a test query page confirmed that result.
I am trying to determine if the old MX Application Pool Defaults set to allow 32bit Applications using .Net Framework v.20 is needed for the CF02016 setting which indicates a default install setting of ;.Net Clr Version of v4.0.
Note: We use a lot of Custom Tags. I have moved all our tags to the new CF 2016 location. Those tags generate most of our data driven pages.
Charlie did note in another forum posting that there are a ton of variables to consider.
AdChoices