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

Record-locking information file (ldb.)

P: 6
Preface: I am using Access 2003 but have Office 2007 on my machine with Access 2007 disabled.
In the database I am working in/building, I transfer data in from SPSS (statistical software) and other access db through ODBC so that I can put into reports in this db.
However, everytime I transfer in data, I get the ldb. that will not go away. Sometimes I can open my mdb., close it and then the ldb. will leave; or open the mdb. close it, and then refresh windows explorer and then it will go away. But mostly, I just cannot get rid of it.
And if I check its properties, I'm the one who has the db open. Or if I try to open and work in my db, it says it is open and locked for editing by another user (me).
Any ideas or solutions??
Thank you in advance.
-Tamela
Apr 24 '08 #1
Share this Question
Share on Google+
6 Replies


NeoPa
Expert Mod 15k+
P: 31,307
Typically, you wouldn't use ODBC to link to an external Access database.

Try connecting using Files of type Microsoft Access.
Apr 25 '08 #2

LBryant
P: 18
Why not use:
Expand|Select|Wrap|Line Numbers
  1. Dim MyOtherDatabase as Database
  2. Set MyOtherDatabase = OpenDatabase("Path to your external DB") 
I don't believe this creates an .ldb lock file. You then can manipulate tables in MyOtherDatabase.
Apr 25 '08 #3

P: 6
Typically, you wouldn't use ODBC to link to an external Access database.

Try connecting using Files of type Microsoft Access.

I am transferring data from SPSS to msAccess, so other than using an ODBC i'm not sure how I would move the data. I'm confused by your suggestion connecting files of type. can you explain further?
thank you!
Apr 25 '08 #4

NeoPa
Expert Mod 15k+
P: 31,307
I'll certainly try.
...
In the database I am working in/building, I transfer data in from SPSS (statistical software) and other access db through ODBC so that I can put into reports in this db.
However, ...
That tells me you are working exclusively with Access databases but using an ODBC connection.
If that's not the case then please ignore the comment, but as you'll see - I was responding to what you'd posted.
If that is the case and you are still confused - let me know and I will go into finer detail.
Apr 25 '08 #5

P: 6
I'll certainly try.

That tells me you are working exclusively with Access databases but using an ODBC connection.
If that's not the case then please ignore the comment, but as you'll see - I was responding to what you'd posted.
If that is the case and you are still confused - let me know and I will go into finer detail.
Thank you.
Its not exclusively Access. One db was built by a contractor in sequel and I link to through ODBC. I use the ODBC to transfer the data into SPSS (Statistical Software for the Social Sciences) and into Access.
Once I score data, i move it from SPSS into Access.
Not my calling in life, but these are the cards dealt...
I wonder if the fact that i'm keeping Access 2003 to finish the db work however having Office 2007 is a factor in the problem?
If not, please ignore.
Thanks again for your help.
Apr 25 '08 #6

puppydogbuddy
Expert 100+
P: 1,923
There are several possible causes of your ldb lock file problem. See these links for possible causes that should be checked out, along with the recommended action to remedy the problem:


You may need to review/change the locking scheme that is configured for the Access DB to No Locks in view if the heavy transaction processing.

http://office.microsoft.com/en-us/ac...408601033.aspx

For example, If you use record-level locking, Access locks only the record you are editing. This becomes the default behavior for access to data through a form, a datasheet, and code that uses a recordset object to loop through records, but not through action queries, nor through code that performs bulk operations using SQL statements, which will lock the entire table being updated.


http://support.microsoft.com/kb/8397...d=2509&sid=898

http://support.microsoft.com/kb/815281

The failure of the ldb file to close could also be a symptom of database corruption. See item # 14 in this link:
http://www.granite.ab.ca/Access/corruption/symptoms.htm
Apr 25 '08 #7

Post your reply

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