Access Security and Windows XP

[D.A. Horn]

I have an application I wrote several years ago in Access
97 which has been updated to 2000. It has user-level
security and its own workgroup, resides on a network
drive, and has worked flawlessly for lo these many years.

Recently, 3 users on the system have upgraded their
computers to Windows XP. They are still running Access
2000 on these computers and opening the database on a
network drive, but when they open the database, none of
the buttons work on the form that contains the start-up
menu.

There are no error messages. The buttons depress when
clicked, but the code behind them does not run. Also, the
code that is supposed to execute On Load and On Activate
does not run. They are basically dead. Strangely, if they
close the form, then open it again, everything is fine.

It gets stranger: This happens when one of the three is
the only user logged on. If someone else is already in,
the database functions normally. If one XP user logs on
and can't function, they can ask another XP user to log
on and the second user is fine. The first user then logs
off and logs back on again and is also fine.

And stranger: All the XP users have full Admin rights. If
the same user logs on using a different name and password
from someone without full rights, the problem vanishes
again. This is using the same Windows XP machine. If the
Win XP user moves to a different computer, one with a
different version of Windows, there is also no problem
logging in.

I've been working with the IT guys and we are at the end
of our collective rope. Any pearls of wisdom from the
newsgroup?

Thanks!
-Dori

 

[C]

Hi Dori,
I don't have an answer to your problem, but I posted a
Windows XP related Access security problem on 7/18 and am
thinking that there is something about XP and Access
security that I am missing (or needs a fix). I too had an
application that was written some time ago that works on
other operating systems and is not working at all in XP.
The users get a typical unauthorized message when they try
to open the application. Supposedly there should have
been a response to my problem in this Managed newsgroup
within 72 hours, but that didn't happen.

 

[D.A. Horn]

Sigh. Why am I not surprised?? )

Thanks for letting me know about your experience, though.
I didn't really have much hope.

-Dori

 

[D.A. Horn]

This is an update to my own question. I have found that
the problem goes away if I change the database
permissions so that the user is unable to open the
database exclusively. Anyone who has the rights to open
exclusive gets the problem.

Also, if the user closes the start-up form and reopens
it, the problem dissappears and they are good to go with
all of their assigned permissions available.

So, I have changed the permissions for 2 of the users who
don't need to open exclusive and the other user is
content to close and reopen the form every time she logs
on. It's a hokey workaround, but it solves the problem
for now.

I still would like to know what the deal is so I can do a
real fix. Anybody got a clue???

-Dori