"Opened Exclusively......". Ever seen that message?

[RoCoPe]

Quick scenario:
I have been managing an Access 97 database on NT for about four years. Database is split, back-end tables, front-end forms, queries, reports, code. Database is used by about 50 people on the network. I do not use Access security, instead, I have user levels defined through code with specific swithboards. These swithboards permit navigation only to predefined areas. Pretty basic, not fancy, works great.

Recently converted to A2000. Now I often receive error messages stating "opened exclusively by "user ID"". What I have discovered, and PLEASE correct me if I am wrong, is the following:

1-Idle database locks other users out.
2-If NT screens saver launches, database is locked (because workstation is locked).
3-If Access is running, but not being used (sitting behind while Word is being used)database becomes locked.

These are just some of my observations. I am not a network guy, and unfortunately, our network guys are not Access guys.

I do have a timer on the database to detect inactivity and close the database. But, nonetheless, I continue to have these same problems.

Anyone's help is greatly appreciated!!!!! RoCoPe
"Learning on the fly"

 

[hermanlaksko]

It looks like the old "Tools/Options/Advanced/Shered" problem.... could it be it?

I have loads of users on single and multi user installations and does not have this problem nore have I seen it.
Herman

 

[RoCoPe]

Thanks for the idea. But, database is in shared mode. This problem only began AFTER converting to Access 2000.

Definetely has something to do with NT or Idle time, or workstation security.

Thanks again!

Any other ideas? RoCoPe
"Learning on the fly"

 

[hermanlaksko]

Could it be that the its the screen saver that is doing this, I gather that you do not have a timer event on this form/app ?
Herman

 

[RoCoPe]

I have determined that the screen saver does cause this scenario. NT screensaver locks the application. I do have a timer on the database, I am testing different time periods of inactivity. One problem is that our company security policy requires screensavers be set at 5 minutes of inactivity. This causes me problems, as people walk away from workstations frequently, and I cannot set the DB timer for five minutes=not very practical.

Additionally, I still have problems with minimized database being locked.

Thanks!! RoCoPe
"Learning on the fly"

 

[hermanlaksko]

Try to have a look at the "sleep" settings, normally found under screen saver, they could be the real meanies, here.
I dont know why but I have seen that "sleeping PCs" can be really hard to wake again.
Also I have notised that if, indeed it is the screen saver, not all savers have thes "extra feature" so try and select a nother saver.
Herman