|
There's a new MS KB article on this exact problem, KB ID Q162357.
According to this article, the problem can have a number of
causes and hence a number of different solutions are described.
The most radical/drastic suggested solution, and the only one
that worked for me, includes deleting your entire
?:\Program Files\Common Files\Microsoft Shared\DAO directory
and then re-installing Access. This does indeed solve the
MS Access Wizards problem, but it also appears to break MS
IIS v3.0 Active Server Pages and/or the Visual InterDev beta if the
IIS server is installed on the same machine as Access '95
(e.g. for development.)
BTW, according to the KB article, the wizards problem can occur
on either NT v4.0 or Windows '95. We haven't seen it on
Windows '95, but then IIS v3.0 only installs on NT v4.0 Server.
You could, I think, see the same problem on Windows '95 with the
PWS HTTP server and ASP.
Before installing Access '95, I had been successfully using
Visual InterDev beta2 and IIS v3.0 ASP on NT v4.0 Intel on my
development machine, using IIS v3.0's ADODB component to access an
Access '95 .MDB file created by someone else, without
having Access '95 installed, using the ODBC drivers installed
by IIS v3.0 ASP. Eventually, I needed to install
Access '95 on my own machine, and when I did so I experienced
the wizards problem discussed here. Following the instructions
in case [4] of the above-mentioned KB article did solve this
problem, but now any IIS v3.0 ASP application (including
the AdventureWorks sample) that use ADODB are broken.
Visual InterDev is still in beta, of course, but IIS v3.0
is a released product. Also Access '95 is a natural adjunct
to IIS v3.0 ASP development. Therefore, I was rather surprised that
there appears to be a co-existence problem. I'm interested in
any possible options anyone else may have discovered. I'm
hoping that there's a solution that doesn't require
upgrading to Access '97, because of the one-way-only
Access '95 to Access '97 database conversion issue.
For now, I'm planning to de-install Access '95, reinstall ASP
and/or the Visual InterDev server options and wait to see
if the version of DAO included with Access '97 is compatible with
IIS v3.0.
|