A
Achez
Good afternoon, all:
I have a database that is shared to a limited group of people using
network level security. The database is based on the Microsoft
template for "Issues". There doesn't seem to be any problem completing
any of the tasks (adding issues, editing records, etc.) in terms of
sharing. However, attempting to open some of the reports will cause
the database to freeze. The rest of the PC operates normally, but the
forms appear to be inactive (pale colour on the title bar), the mouse
cursor remains a pointer (no hourglass), and the database doesn't
respond to keystrokes or mouse clicks. Using the task manager is the
only way to quit the database, but the application appears as "Running"
in the task manager. This seems to happen regardless of whether
someone else is using the database or not. Since the database window
is hidden, the reports are designated as pop-up - this problem is
occuring on both the XP and 2003 versions of Office, and the database
is in Access 2000 format. What seems odd is that it's only 3 of 9
reports that are troublesome, but they were all created the same way.
Any help at all is greatly appreciated!
Thanks,
Achez
I have a database that is shared to a limited group of people using
network level security. The database is based on the Microsoft
template for "Issues". There doesn't seem to be any problem completing
any of the tasks (adding issues, editing records, etc.) in terms of
sharing. However, attempting to open some of the reports will cause
the database to freeze. The rest of the PC operates normally, but the
forms appear to be inactive (pale colour on the title bar), the mouse
cursor remains a pointer (no hourglass), and the database doesn't
respond to keystrokes or mouse clicks. Using the task manager is the
only way to quit the database, but the application appears as "Running"
in the task manager. This seems to happen regardless of whether
someone else is using the database or not. Since the database window
is hidden, the reports are designated as pop-up - this problem is
occuring on both the XP and 2003 versions of Office, and the database
is in Access 2000 format. What seems odd is that it's only 3 of 9
reports that are troublesome, but they were all created the same way.
Any help at all is greatly appreciated!
Thanks,
Achez