How do I stop a user blocking other users inadvertantly

[SIGIR]

I've deployed a simple access 2003 application (forms, queries, VBA etc...) with tables linked to SQL server backend (saved userid and password). It is located in common group folder. Worked fine for 2 years. User group is only 10 people.

Recently, when a single user opens the application, other users are blocked from entering the application. Other users Double-clicking the application get no response whatsoever. An .ldb file is created and displays the computername of the blocking user. I can't seem to find a way circumvent this.

We are on a very restricted server within a government agency and I know something must have changed effecting security levels. I just can not narrow down the issue to determine a course of action. Any help would be appreciated.

 

[MMSMSD]

Have you checked your MACRO SECURITY settings? I have seen that some of the more recent Office updates automatically set it HIGH, which can cause databases to do wierd things like that. Hope this helps.

 

[SIGIR]

The Macro security setting only effects the users computer. Also, I made sure none were set to high. This promlem is really stumping me. I'm having to have each user use a copy of the program. This causes update issues with any changes I make to the code.

Anyone else have any suggestions?

 

[BoxHead]

Have you checked the record-locking settings (and other settings) under TOOLS>OPTIONS Advanced tab?

These settings seem to apply to the Access installation not just the database on which changes are made.

HTH

John




Life is short.
Build something.

 

[SIGIR]

I have "No Locks" checked.
Also checked is "Open databases using record-level locking"
Open mode is "Shared"

Good suggestion though.

 

[BoxHead]

Sorry it didn't help.

It sounds like you have multiple users using copies instead of just the "problem" user. That suggests that there may be something special about this person? Is this user logged in as the SQL Administrator? The Network Administrator? Are there other programs hitting the SQL Server without issue when this particular user is logged in?

I know that with Outlook there are 'known issues' around users having one e-mail ID and a different network ID. It might be worth listing out the saved login IDs and their respective rights.

Last thought... looking again at the "Advanced" tab, make sure the intervals for refreshing are aligned between the machines. I'm just thinking that if a 1500 second interval for ODBC Refreshing got changed to 1 second, it could lock things up pretty tight.



John






Life is short.
Build something.

 

[SIGIR]

The copies were a work around. It's not just 1 user locking up the rest, if any 1 person gets in the others are blocked. In addition, it does not even produce a message. They double-click on the shortcut and get no message what-so-ever.

I'll look at the permissions and intervals. How does the fact of being a network administrator effect it? None of them are, just wondering.

 

[danvlas]

Just a thought...

Do you have any transaction open over the connection?




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[Hakala]

I use a frontend/backend shortcut solution for this. We had a lot of problems with users being locked out, and this has resolved it. For info:

http://www.granite.ab.ca/access/autofe.htm

In short form:
The database will be in a new folder and only the shortcut will be in the original database folder. The shortcut, working with AutoFeUpdater above and an .ini file, copies the frontend to the user's machine. Only the backend tables are shared.

It's working really well for us. I especially like it because I can make changes to the frontend (designing of reports and forms) when users are working in the database. Only changes to the tables themselves are still restricted.

If you have a place I can send files, I can send you any examples you'd need. Good luck!

 

[adalger]

Have you checked your users' Access installation Default Open Mode? It might have been inadvertently changed from Shared to Exclusive.