J
Jeff Vandervoort
My client's in-house Access developer created an MDB application that is
shared by perhaps 100 users (total, not simultaneously). MDB is in Access
2000 format, but is used in Access 2003 w/ and w/o SP1 on Win XP SP1 and SP2
computers. The MDB runs queries against a database on a SQL 2000 Server.
2 users have had a problem develop that causes the queries to fail. No error
messages, no nothing. They click the buttons on the custom forms to start
the reports, and any subforms or input boxes that are required to build the
query work, but when the actual query is executed, there is an hourglass
pointer for a few seconds, and then nothing.
It gets weirder: If another user with identical permissions on the MDB and
the database logs on to the same computer, the app works. If the user with
the problem logs on to a different computer (roaming profiles are in use),
it works.
The only time it fails is when the user logs on to their own computer.
Deleting the locally cached user profile and letting Windows download a new
copy from the server doesn't help. Doing a repair install for Access &
Office doesn't help. Uninstall/reinstall Office doesn't help.
The problem does not coincide with any particular upgrade or config change
on the 2 machines. In fact, most such changes are pushed via GPO and SUS, so
they tend to happen at more-or-less the same time across the system, but
these two incidents happened months apart.
I'm not sure where to go with this...any ideas?
shared by perhaps 100 users (total, not simultaneously). MDB is in Access
2000 format, but is used in Access 2003 w/ and w/o SP1 on Win XP SP1 and SP2
computers. The MDB runs queries against a database on a SQL 2000 Server.
2 users have had a problem develop that causes the queries to fail. No error
messages, no nothing. They click the buttons on the custom forms to start
the reports, and any subforms or input boxes that are required to build the
query work, but when the actual query is executed, there is an hourglass
pointer for a few seconds, and then nothing.
It gets weirder: If another user with identical permissions on the MDB and
the database logs on to the same computer, the app works. If the user with
the problem logs on to a different computer (roaming profiles are in use),
it works.
The only time it fails is when the user logs on to their own computer.
Deleting the locally cached user profile and letting Windows download a new
copy from the server doesn't help. Doing a repair install for Access &
Office doesn't help. Uninstall/reinstall Office doesn't help.
The problem does not coincide with any particular upgrade or config change
on the 2 machines. In fact, most such changes are pushed via GPO and SUS, so
they tend to happen at more-or-less the same time across the system, but
these two incidents happened months apart.
I'm not sure where to go with this...any ideas?