T
Terri
I have a setup where remote users are running Access 2000
on Windows XP and Windows 2000 computers. They have
access to our server and to our Access 2002 databases
(These databases are 2000 compatible.) The databases
have user-level security.
They can get to the opening menu, but just recently, they
have started getting "Microsoft Access for Windows has
encountered a problem and needs to close" (XP)
or "MSACCESS.EXE has generated errors..." (2000) errors
when they click on a button on the form which uses the
OpenForm command to go to another form. None of my local
users are getting this error.
So far, I've checked the network rights of the remote
users, they appear to be ok (I can log in as them from my
computer and access the dbs fine.) We both (local and
remote) appear to be using the same Reference Libraries.
I checked to see that the DAO360.dll file was registered,
run Compact/Repair. It does seem that, with three
databases all not working, there must be something
incompatible with their general setup. I did notice that
they have not upgraded to the SP-3 patch for Office -
could this be causing the problem?
Has anyone run into this problem? Help!! Thanks - Terri
..
on Windows XP and Windows 2000 computers. They have
access to our server and to our Access 2002 databases
(These databases are 2000 compatible.) The databases
have user-level security.
They can get to the opening menu, but just recently, they
have started getting "Microsoft Access for Windows has
encountered a problem and needs to close" (XP)
or "MSACCESS.EXE has generated errors..." (2000) errors
when they click on a button on the form which uses the
OpenForm command to go to another form. None of my local
users are getting this error.
So far, I've checked the network rights of the remote
users, they appear to be ok (I can log in as them from my
computer and access the dbs fine.) We both (local and
remote) appear to be using the same Reference Libraries.
I checked to see that the DAO360.dll file was registered,
run Compact/Repair. It does seem that, with three
databases all not working, there must be something
incompatible with their general setup. I did notice that
they have not upgraded to the SP-3 patch for Office -
could this be causing the problem?
Has anyone run into this problem? Help!! Thanks - Terri
..