Fatal error when accessing control button on form

  • Thread starter Thread starter Terri
  • Start date Start date
T

Terri

I have a setup where remote users are running Access 2000
on Windows NT 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" errors when
they click on a button on the form which uses the
OpenForm command to go to another form. They've also had
the "MSACCESS.EXE has generated erros..." message.

None of my local users are getting this error. 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.) I'm suspecting some
Windows/Office setup incompatibilities and am searching
the Knowledge Base. I've checked the Dao360.dll file,
and it seems to be ok.

Has anyone run into this problem? Help!! Thanks - Terri
 
I've seen this many times and I've created the problem
each time. In my case I created a Utilities.mde file which
the front end (FE.mde) uses. Now the problem is that when
I update the Utilities.mde file by creating a new mde, I
need to create a new FE.MDE so it can reference it
properly. Now what happens is that the local users have
access to the latest version of the both files, yet the
remote uses only get the updated FE.MDE and therefore
being unable to find the proper Utilities.mde file, it
crashes access. The best way to test for this is to open
the *FE.MDB* on the remote users machine and check the
references. You may not be referencing a .MDE but you may
be missing another referenced file.
 
Thanks, Cheval.

However, I don't think this applies to my situation. All
users get access to the same front-end (although I know
that is not the ideal scenario; there are other reasons
why I've done this.) I did not create a new back-end
prior to this happening.

I'm starting to think this may have to do with an NT
login problem which I need to discuss with my network
admin. Also, I discovered that these users have not
upgraded to the latest SP3 patch for Office 2000; I'm
going to try this as well.

Thanks again - any other ideas/suggestions are still
appreciated!! Terri
 
Back
Top