Access 'Database In Use' Problems (also posted in microsoft.public.access)

microsoft.public.dotnet.framework.adonet

26 Apr 2006 11:17 AM

ChrisM

Hi,

Apologies for posting the same message in 2 different newsgroups, but I
didn't know about this one until after I had already posted in the Access
NG. Any complaints to rubbish***@junkyRubbish.com ;-)

Anyway...

I have a dotNet, C# application with about 10 users (Windows Forms, not ASP)
..
The basic setup is that each user has a copy of the program on their PC
which uses a local(ie on their PC) access database which contains the
queries and a set of linked tables that link to the actual datatables on a
single 'master' database which lives on the server.
So each user has a copy of the application and a copy of the 'queries'
database which all link to one 'data' database.
This is the connection string used to connect to the local 'queries'
database:
"Provider=Microsoft.Jet.OLEDB.4.0;Password="""";User ID=Admin;Data
Source=.\MyDb.mdb;Mode=Share Deny None;Extended Properties="""";Jet
OLEDB:System database="""";Jet OLEDB:Registry Path="""";Jet OLEDB:Database
Password="""";Jet OLEDB:Engine Type=5;Jet OLEDB:Database Locking Mode=1;Jet
OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet
OLEDB:New Database Password="""";Jet OLEDB:Create System Database=False;Jet
OLEDB:Encrypt Database=False;Jet OLEDB:Don't Copy Locale on
Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet
OLEDB:SFP=False";
It seems long, but I lifted it from somewhere else, and I'm not sure what
all the parameters actually do...
The problem is I am getting 'Database In Use' errors, not all the time, but
a few times a week. It even seems to happen if UserA is accessing one table
and UserB is accessing a totally unrelated one. Also, if I open a copy of
the 'queries' database on my PC and run a query then EVERYONE else gets a
Database In Use error if their copy of the application tries to access the
data. Please can anyone help me sort this out?
One other piece of information that may be relevant is the the problem is
worse since we upgraded our server operating system from NT4 to Microsoft
SBS2003.

Any suggestions or advise most gratefully received.

Thanks,

Chris.