Jet OLEDB: Database Locking Mode
From: Andy Willis (andrewrwillis_at_blueyonder.co.uk)
Date: 01/25/05
- Next message: Geoff Jones: "Q: Finding Records"
- Previous message: steven scaife: "copying recordset from one database into a copy of the database"
- Next in thread: Marc Doolittle: "Re: Jet OLEDB: Database Locking Mode"
- Reply: Marc Doolittle: "Re: Jet OLEDB: Database Locking Mode"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 25 Jan 2005 10:40:56 -0000
The Jet OLEDB: Database Locking Mode is set to 1 in the Advanced tab of the
Connection to my Access MDB on my import DTS Local Package.
I have not been able to find what this setting is or any other for that
matter
My problem is that my DTS package runs fine as a scheduled job if noone is
in the MDB database but fails if someone is in the MDB. This makes me think
that for some reason the SQL DTS job is trying to open the Access database
exclusively before it does the data import.
Also what should the Mode setting be as a number for shared access.
I guess this could also be a problem amending the LDB if someone else has
already created it, but I think that unlikely because if the LDB can be
created (scheduled job runs fine of noone in MDB) then you would expect it
to be able to be amended.
Regards
Andy Willis
- Next message: Geoff Jones: "Q: Finding Records"
- Previous message: steven scaife: "copying recordset from one database into a copy of the database"
- Next in thread: Marc Doolittle: "Re: Jet OLEDB: Database Locking Mode"
- Reply: Marc Doolittle: "Re: Jet OLEDB: Database Locking Mode"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|