J
JimS
This is crazy. My client installed a new user last week. Everything about the
install is vanilla. He's executing a FEdb located on a network by using
Tony's AutoFE to copy it to a local drive. The BEdb is on the network. Up
until this new guy was installed, everything was going fine.
The new guy (Tom) executes the Autofe shortcut from his desktop and the
Autofe process works peachy, except HE LOCKS THE MASTER FEdb! The lock lasts
for 10-20 minutes, then disappears magically. I can't tell exactly what he's
doing, but my users all have menus they work from. He's a clerk, so he's even
less likely to do something hinkey (especially after I've yelled at him
repeatedly...)
When I check his Access properties, all is good. No references I can see to
the FEdb. All the tables are linked to the backend...there are no permanent
local tables at all. In his case, no local tables at all....
Tony, any idea?
install is vanilla. He's executing a FEdb located on a network by using
Tony's AutoFE to copy it to a local drive. The BEdb is on the network. Up
until this new guy was installed, everything was going fine.
The new guy (Tom) executes the Autofe shortcut from his desktop and the
Autofe process works peachy, except HE LOCKS THE MASTER FEdb! The lock lasts
for 10-20 minutes, then disappears magically. I can't tell exactly what he's
doing, but my users all have menus they work from. He's a clerk, so he's even
less likely to do something hinkey (especially after I've yelled at him
repeatedly...)
When I check his Access properties, all is good. No references I can see to
the FEdb. All the tables are linked to the backend...there are no permanent
local tables at all. In his case, no local tables at all....
Tony, any idea?