Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login
Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Tek-Tips LinkedIn® Group

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...with companys cutting back on training, lack of true support by makers of software, the forums are a great tool in your cyber-toolbox...."
More...

Geography

Where in the world do Tek-Tips members come from?
Click Here To Find Out!

Tek-Tips Shirts!

Get Tek-Tips Swag
Get your
Tek-Tips Forums
SWAG here!
Home > Forums > Programmers > DBMS Packages > Microsoft: Access Other topics Forum

Access 2010 to 2003

thread181-1686840
Read More Threads Like This One
NWTrust (TechnicalUser)
26 Jun 12 16:12
I have written an Access database in 2010 to be run on a 2003 system. The database (.accdb)ran with no problems on my machine. I converted it to 2003 (.db) and it ran with no problems on my machine. However, on installing it on the machine it was intended for (2003) although it ran with no problem, on closing a message "Access has encountered a problem and needs to close" appears. I also notice that the .ldb file remains. Both machines are running Win 7.
Any help on this would be greatly appreciated.
NWTrust (TechnicalUser)
26 Jun 12 16:17
.db should, of course, read .mdb
cimoli (TechnicalUser)
27 Jun 12 11:22
I have encountered the same. I don't know why. To get around it, I copy my Access file to another name. Then I delete the old one and also the 1 KB .ldb file Then i use the newer file name and i am okay again. I encountered this on both a windows xp lan and also my standalone home machine. Maybe someone knows the real reason.
Read More Threads Like This One

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Back To Microsoft: Access Other topics

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close