Results 1 to 5 of 5
  1. #1
    5 Star Lounger st3333ve's Avatar
    Join Date
    May 2003
    Location
    Los Angeles, California, USA
    Posts
    705
    Thanks
    0
    Thanked 2 Times in 2 Posts

    Danger Exporting to Library Database (A2K (SP-2))

    <img src=/S/nope.gif border=0 alt=nope width=15 height=15> Ouch! Let me report on this mishap while it's still fresh.

    I have a library database (an .mdb) file that I use by setting a Reference to it in other databases. I just exported a form and a separate module from one of those other databases to the library database. Then, when I went to close the former database, the code that runs when I hit the Exit button broke with an "out of memory" error. After I managed to get that database closed and opened the library database, I found that the library database was missing all modules other than the one I'd just exported to it. (The handful of forms in the library database were still there and could be opened, but their modules were gone.) The missing modules showed up in the database window, but when I tried to open any of them I got a message that there was no module with that name, and they didn't show up in the Project Explorer in the VBE window. When I tried to compact and repair the library database, Access just froze.

    Fortunately I was freshly backed-up, so I'm back in business. I'm guessing the moral of the story may be: If you want to export from Database X to a library database that Database X uses by Reference, don't export, import -- that is, close Database X, open the library database and import from Database X.

    I'd be interested in knowing if anyone else has any light to shed on this experience. I should add that I'm 98% sure I've exported from Database X to the library database in the past without running into trouble, so I'm pretty sure the maneuver is not inevitably fatal, but I'm not keen to try any further experimentation myself.

  2. #2
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: Danger Exporting to Library Database (A2K (SP-2))

    I have heard of this happening before; that is, I've heard of someone having the same problems with a database, though I don't know if it came from doing an export. Lucky you had good backup, because I understand the problem is non-recoverable.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Danger Exporting to Library Database (A2K (SP-2))

    Upgrade your Office 2000 to SR-3. It sounds like you have run into the conflict between the vbe6.dll installed by Office 2000 and the version installed by OXP applications. That typically shows up when you import or export code containers like forms and modules. You can't necessarily fix the toasted database, but the patch in SR-3 should keep it from happening again.
    Charlotte

  4. #4
    5 Star Lounger st3333ve's Avatar
    Join Date
    May 2003
    Location
    Los Angeles, California, USA
    Posts
    705
    Thanks
    0
    Thanked 2 Times in 2 Posts

    Re: Danger Exporting to Library Database (A2K (SP-2))

    Thanks for the reply, although it sounds like I probably goofed by putting "A2K" in my message header. I'm using all my databases in Access 2000 format, but I'm running Office XP (i.e., Access 2002) and Windows XP. (Those were both fresh installs on my computer, which I bought in December, rather than upgrades from previous versions of Windows or Office.) And my version of Access 2002 is SP-2.

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Danger Exporting to Library Database (A2K (SP-2))

    In that case, I don't have a clue. I've never seen that kind of behavior in AXP, regardless of file format. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

Posting Permissions

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