Joe8915
Registered User.
- Local time
- , 22:41
- Joined
- Sep 9, 2002
- Messages
- 820
Running Windows 7
SQL BE
Access FE
Running on a Network
Office 2010
Here is my issue. I just had Windows 7 installed, had XP prior. The db gets an error msg that it was closed un-expertly. After I make the changes in the db, I compact and Repair What happens the ldb file is still there when closed. When that happens in XP, I just deleted the file and went on without a hitch. This only happens when I modify the db.
I have a security file when the users log on, which is located on the network in another file. I see the ldb file there when I close my file. I believe I will have that file whenever a user is logged into the db. I was thinking to delete that file, but I held off on that idea.
I did notice when I log into the production db, which is located on the network, I will get the same error. So then what I do is delete the db on the network and log off the computer and log back on and the db is ok. I have a script running whenever you log off and log back on a new db is inserted.
I hope I made some since. Any Ideas?
Just wanted to say thanks to all who is ever help me out. Just seems I don't say it enough
SQL BE
Access FE
Running on a Network
Office 2010
Here is my issue. I just had Windows 7 installed, had XP prior. The db gets an error msg that it was closed un-expertly. After I make the changes in the db, I compact and Repair What happens the ldb file is still there when closed. When that happens in XP, I just deleted the file and went on without a hitch. This only happens when I modify the db.
I have a security file when the users log on, which is located on the network in another file. I see the ldb file there when I close my file. I believe I will have that file whenever a user is logged into the db. I was thinking to delete that file, but I held off on that idea.
I did notice when I log into the production db, which is located on the network, I will get the same error. So then what I do is delete the db on the network and log off the computer and log back on and the db is ok. I have a script running whenever you log off and log back on a new db is inserted.
I hope I made some since. Any Ideas?
Just wanted to say thanks to all who is ever help me out. Just seems I don't say it enough