By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,946 Members | 697 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,946 IT Pros & Developers. It's quick & easy.

Can Access Cause Share Locks in SQL Server if Account is Read Only

P: 1
Is there a problem with linked tables in Access causing share locks in SQL server if my SQL Server account has read only permissions?

The IT group I work with has a negative view of Access. I use Access to query Oracle and SQL Server data sources for most of my ad hoc data needs.

I hear quite often to "be careful" when using Access to read sql server data becasue it can cause share locks in sql server.
My response has always been, then configure SQL Server better so that I can't lock the records and if it can't be done, let's get a real database that can handle it. To which of course, I usually get a grunt and nothing more.

We are using Access2003 against SQL Server
Mar 21 '07 #1
Share this Question
Share on Google+
1 Reply


MMcCarthy
Expert Mod 10K+
P: 14,534
Is there a problem with linked tables in Access causing share locks in SQL server if my SQL Server account has read only permissions?

The IT group I work with has a negative view of Access. I use Access to query Oracle and SQL Server data sources for most of my ad hoc data needs.

I hear quite often to "be careful" when using Access to read sql server data becasue it can cause share locks in sql server.
My response has always been, then configure SQL Server better so that I can't lock the records and if it can't be done, let's get a real database that can handle it. To which of course, I usually get a grunt and nothing more.

We are using Access2003 against SQL Server
I haven't heard of any problems with this and have worked on a number of these systems although mostly with Access 2000.

Mary
Mar 21 '07 #2

Post your reply

Sign in to post your reply or Sign up for a free account.