BUG: MS Access 7.0a conflict
Dan Melchione
Attempting to run MS Access 7.0a ( from a clean install NT 4.0 beta 2
[ build 1314 ] ) results in a dialog box with the message "Microsoft
Access can't start the data access object (DAO) and so it can't
continue." After clicking OK, the program terminates.
I contacted MS Access product support and they said it was a problem
in NT 4.0.
Adrian Kwong
da...@internal.mcafee.com (Dan Melchione) wrote in article
<31b78118...@nntp.best.com>...
Run MS Access as an Administrator. It should work better. :) I have
found that unless you have Administrator access, half of the MS Access
functions won't work correctly.
I only have NT4.0b2 installed, and it's the only way I can run the
Wizards to create new databases.
--
==========================================================================
Adrian Kwong bur...@netcom.ca 819-568-4568
Bald Mountain Ent. ak...@freenet.carleton.ca Gatineau, Quebec
<The Happy Fun Fox was here!> <everything else is just 8 bit!>
==========================================================================
Alfred Moussali
> da...@internal.mcafee.com (Dan Melchione) wrote in article
<31b78118...@nntp.best.com>...
> Attempting to run MS Access 7.0a ( from a clean install NT 4.0 beta 2 [
build 1314 ] ) results in a dialog box with the message "Microsoft Access
can't start the data access object (DAO) and so it can't continue." After
clicking OK, the program terminates.
>
> I contacted MS Access product support and they said it was a problem in
NT 4.0.
>
>
Got the same problem, I tried reinstallation checked for duplicate files
in the windows directory; followed all the recommendations on KB to no
avail.
I'm convinced there is a bug in WinNT 4.0B2 that gives an "exception
access violation" each time you try to open any database.
If somebody happens to know a workaround please let us know.
Phil
Just upgraded to B2 and Access works on my system just fine. So, I don't
think that it's a bug in NT 4.0. May have something to do with your
particular configuration, hardware, etc.
Chris Crabtree
"Alfred Moussali" <Mos...@ix.netcom.com> writes: >
>
> > da...@internal.mcafee.com (Dan Melchione) wrote in article
> <31b78118...@nntp.best.com>...
> > Attempting to run MS Access 7.0a ( from a clean install NT 4.0 beta 2 [
> build 1314 ] ) results in a dialog box with the message "Microsoft Access
> can't start the data access object (DAO) and so it can't continue." After
> clicking OK, the program terminates.
> >
> > I contacted MS Access product support and they said it was a problem in
> NT 4.0.
> >
> >
> Got the same problem, I tried reinstallation checked for duplicate files
> in the windows directory; followed all the recommendations on KB to no
> avail.
>
> I'm convinced there is a bug in WinNT 4.0B2 that gives an "exception
> access violation" each time you try to open any database.
>
> If somebody happens to know a workaround please let us know.
I've got Visual Basic Enterprise Edition and Visual C++ Professional
4.0 installed on my system, and I don't have any problems with
Access95. My guess is that, since VB installs DAO stuff, it's there
for Access95 as well. Those files are redistrubatable, I think, so
you can probably download them from Microsoft somewhere...
Andy Hochstetler
> I've got Visual Basic Enterprise Edition and Visual C++ Professional
> 4.0 installed on my system, and I don't have any problems with
> Access95. My guess is that, since VB installs DAO stuff, it's there
> for Access95 as well. Those files are redistrubatable, I think, so
> you can probably download them from Microsoft somewhere...
>
Same here...I've been using Access 7.0 with almost no problems on Beta 2. I do have a small glitch with the AutoFormat function not working though. It gives an error that says "Application-defined or Object-defined Error.", then bombs out.
I guess there are still some small problems. At least it runs where the beta shell for 3.51 didn't run at all.
Simon Fairbourn
In article <4pkg22$e...@usenet10.interramp.com>, Andy Hochstetler
<and...@interramp.com> writes
> I do
>have a small glitch with the AutoFormat function not working though. It gives
>an error that says "Application-defined or Object-defined Error.", then bombs
>out.
>
a form with only the key field properly added. Non-key fields are either
missing or are presented as lines and I have to manually change them to
proper fields.
--
Simon Fairbourn