Access ldb file has the wrong file type association, ie, wrong icon

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • marvin99
    New Member
    • May 2024
    • 1

    Access ldb file has the wrong file type association, ie, wrong icon

    I inadvertently opened an Access ldb file with Notepad and now the file type icon changed from Access to Notepad. How can I restore the correct one?
  • jimatqsi
    Moderator Top Contributor
    • Oct 2006
    • 1290

    #2
    You needn't worry about that. It is probably a .txt copy of the .ldb file, and so it is of no consequence. When you start Access that .ldb file is created and when you close out it should be deleted. It doesn't always get deleted and I don't know why. But it is recreated the next time you start Access.

    Comment

    • NeoPa
      Recognized Expert Moderator MVP
      • Oct 2006
      • 32636

      #3
      Hi Jim.

      The issue described is that the file association for LDB files has been updated to use Notepad now, instead of whatever it was before - presumably something related to Access. As you know, I'm sure, this is hardly a problem, as LDB files (& LACCDB ones of course) were never designed to be opened directly by anything. Instead they are created and (usually) deleted by Access whenever a database file is opened. They're associated/linked files which have no meaning except when the related database is open.

      It is possible to reset the file association but I don't have the details to hand. To be honest I'm not inclined to dig them up for this example because - as already mentioned - it's never used.

      @Marvin.
      As Jim suggested, simply delete any LDB (LACCDB) files you have left over once Access is closed (for the related database) and open any databases you have in the normal way. A new LDB (LACCDB) file will be created for you at this time and deleted later once the database is closed.

      Comment

      • jimatqsi
        Moderator Top Contributor
        • Oct 2006
        • 1290

        #4
        Neopa, thank you for clearing that up. I didn't read very well the original post. Understanding the problem is a requirement to fixing the problem

        Comment

        Working...