Results 1 to 11 of 11

Thread: Can't Open Database Error 3041

  1. #1

    Thread Starter
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,431

    Can't Open Database Error 3041

    I use the following DAO code to open a database
    VB Code:
    1. DBEngine.SystemDB = GetWindowsDir() & "WIZARD.MDA"
    2.     DBEngine.DefaultUser = "MyUserName"
    3.     DBEngine.DefaultPassword = "MyPassword"
    4.     gsRWTSPath = App.Path & "\data\rwts.mdb"
    5.     Set gdbRWTS = Workspaces(0).OpenDatabase(gsRWTSPath)
    After literally years of maintaining this application I'm suddenly getting error 3041 which says "Can't open a database created with a previous version of your application". What in the world is going on? (I can't find any reference to the 3041 error in help.)

  2. #2
    PowerPoster techgnome's Avatar
    Join Date
    May 2002
    Posts
    34,687
    By any chance was Access reciently upgraded? That error message looks similar to the message Access displays when a DB has been updated to a newer version, then an attempt is made to open it in an older version.
    IE: DB was created using Access2K, "upgraded" to AccessXP, then tried to open it using Access2K....
    For some reason, MS in their infinite wisdon didn't maintain backwards compatibility. Once an Office doc (Word, PP, Access, XL) is converted to XP, there's no going back.


    Just a guess tho.
    * I don't respond to private (PM) requests for help. It's not conducive to the general learning of others.*
    * I also don't respond to friend requests. Save a few bits and don't bother. I'll just end up rejecting anyways.*
    * How to get EFFECTIVE help: The Hitchhiker's Guide to Getting Help at VBF - Removing eels from your hovercraft *
    * How to Use Parameters * Create Disconnected ADO Recordset Clones * Set your VB6 ActiveX Compatibility * Get rid of those pesky VB Line Numbers * I swear I saved my data, where'd it run off to??? *

  3. #3

  4. #4
    Hyperactive Member goatsucker's Avatar
    Join Date
    Dec 2002
    Location
    Leeds, England
    Posts
    283
    What about database corruption? I must admit I have not seen that error turn up due to a Jet 3.x database corrupting, but it might be worth repairing the database. It is the sort of thing that can turn up out of the blue.
    After all "Rust Never Sleeps"

  5. #5

    Thread Starter
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,431
    I tried that already. It seems that it has something to do with the MDA file because when I bypass the DbEngine stuff I can open the main database. That doesn't do me any good however because the tables are password protected and so I can't read them without executing the DbEngine code.

    Any idea how to create an MDA file? I must have done it before since one exists for this app, but I don't remember how.

  6. #6
    Addicted Member
    Join Date
    Jul 2002
    Posts
    234
    I'm not sure if this helps, but this is from the MSDN Knowledge base:

    http://support.microsoft.com/default...;en-us;q152216

  7. #7

  8. #8
    Addicted Member PhilRob56's Avatar
    Join Date
    Oct 2002
    Location
    New York
    Posts
    249
    Early versions of Access use an MDA file, with Access 97 and later using an MDW file for security.

    If Access is installed then look for a file called WRKADM.EXE (or similar name) in your Windows System directory.
    You use this file to create or join the Workgroup. You will probably need to rename the existing MDA file first..(sorry for stating the obvious )
    Some days you're the dog,
    and some days you're the hydrant.


    VB6 Enterprise

  9. #9

  10. #10

    Thread Starter
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,431
    Originally posted by PhilRob56
    Early versions of Access use an MDA file, with Access 97 and later using an MDW file for security.

    If Access is installed then look for a file called WRKADM.EXE (or similar name) in your Windows System directory.
    You use this file to create or join the Workgroup. You will probably need to rename the existing MDA file first..(sorry for stating the obvious )
    I'm familiar with the Workgroup Administrator (wrkadm). I have an MDW file that is associated with another app. When I use the Workgroup Administrator and join either that MDW file or my MDA file I get the same error message when I try to start Access! I can however join System.MDW. What do I do from there?

  11. #11

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width