C
Craig
Hello,
I have a Access 2000 database that is split (FE/BE) and is being used by
approximately 15-20 people over a company network. User-level security is
present. Only about 5 of the users have the ability to add data; the rest
are simply viewing records and running reports. All of the users are running
the database using Access 2003 in runtime mode.
One user came to me with a problem yesterday wherein anytime she would try
to run a report (i.e., display the report in preview mode) the database would
crash with the following message:
"Microsoft Access for Windows has encountered a problem and needs to close.
We are sorry for the inconvenience."
The dialog box gives you the option to debug or report the error; clicking
"debug" causes Microsoft Access to shut down with no further action.
Worse, when the same user restarts the database, the same error also occurs
whenever she tries to use drop-down menus that would execute VBA code. (The
drop-down errors do not occur until the report error mentioned above
"corrupts" the file, so to speak, which I have tested by replacing a copy of
her FE with a "clean" copy.)
Even more puzzling, these errors are occurring on her computer alone. Other
users can run the reports and use the drop-down menus with no problem, and
she can log in on other computers and use the reports and drop-downs with no
problem.
Another factor is that if I run her FE in Microsoft Access (i.e., not in
runtime mode), none of the errors occur and everything works fine on her
computer.
All of this leads me to believe that the error is being caused by at least
one of the following:
1. Her computer or Microsoft Office on her computer
2. Access runtime mode
Since the initial error seems to be caused by attempting to run a report, I
tried connecting her computer to several different network printers, but the
error still occurred with each one, which leads me to believe it is not
necessarily a printer-related problem.
I have also tried compacting and repairing the FE, with no luck. It will
fix the drop-down errors, but the report-preview errors still occur, after
which the drop-down errors reappear.
Lastly: I have done some research about this on other Internet Access
forums. I am having a hard time finding someone else who has encountered
this exact problem, although a similar problem (resulting in roughly the same
error message) seems to have been caused by a corrupt dao360.dll file. The
solution was apparently to uninstall and reinstall Microsoft Office (or
Microsoft Access) to repair the corrupt file. Not sure if that sheds any
light on what might be causing this problem, or whether a simpler solution
might be simply to copy the dao360.dll file over from a machine that is
working?
Any help is GREATLY appreciated!
Craig
I have a Access 2000 database that is split (FE/BE) and is being used by
approximately 15-20 people over a company network. User-level security is
present. Only about 5 of the users have the ability to add data; the rest
are simply viewing records and running reports. All of the users are running
the database using Access 2003 in runtime mode.
One user came to me with a problem yesterday wherein anytime she would try
to run a report (i.e., display the report in preview mode) the database would
crash with the following message:
"Microsoft Access for Windows has encountered a problem and needs to close.
We are sorry for the inconvenience."
The dialog box gives you the option to debug or report the error; clicking
"debug" causes Microsoft Access to shut down with no further action.
Worse, when the same user restarts the database, the same error also occurs
whenever she tries to use drop-down menus that would execute VBA code. (The
drop-down errors do not occur until the report error mentioned above
"corrupts" the file, so to speak, which I have tested by replacing a copy of
her FE with a "clean" copy.)
Even more puzzling, these errors are occurring on her computer alone. Other
users can run the reports and use the drop-down menus with no problem, and
she can log in on other computers and use the reports and drop-downs with no
problem.
Another factor is that if I run her FE in Microsoft Access (i.e., not in
runtime mode), none of the errors occur and everything works fine on her
computer.
All of this leads me to believe that the error is being caused by at least
one of the following:
1. Her computer or Microsoft Office on her computer
2. Access runtime mode
Since the initial error seems to be caused by attempting to run a report, I
tried connecting her computer to several different network printers, but the
error still occurred with each one, which leads me to believe it is not
necessarily a printer-related problem.
I have also tried compacting and repairing the FE, with no luck. It will
fix the drop-down errors, but the report-preview errors still occur, after
which the drop-down errors reappear.
Lastly: I have done some research about this on other Internet Access
forums. I am having a hard time finding someone else who has encountered
this exact problem, although a similar problem (resulting in roughly the same
error message) seems to have been caused by a corrupt dao360.dll file. The
solution was apparently to uninstall and reinstall Microsoft Office (or
Microsoft Access) to repair the corrupt file. Not sure if that sheds any
light on what might be causing this problem, or whether a simpler solution
might be simply to copy the dao360.dll file over from a machine that is
working?
Any help is GREATLY appreciated!
Craig