Results 1 to 4 of 4
  1. #1
    New Lounger
    Join Date
    Mar 2003
    Location
    Frederick, Maryland, USA
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    ghost forms (Access 2000)

    I've had a number of forms get corrupted thanks to a pesky network error problem. I've deleted the forms, but they still reside on the VBA side. Now I'm unable to compact and repair the database because of these "ghost" forms. Anyone have any experience getting rid of them in VBA?

    Thanks,
    Craig aka OfficeProWannabe

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: ghost forms (Access 2000)

    Is this a frontend database in a frontend/backend setup? In that case, replace the corrupt database with a non-corrupt copy or with a recent backup.

    If the database contains both tables and other objects, and if you have not changed the design of forms and reports recently (or not much), you can retrieve a backup from before the corruption, delete all tables, then import the tables from the corrupt database.

    If you don't have a suitable backup, create a blank new database and import all database objects from the corrupt database (or as many as possible). You will have to set the startup properties for the database manually.

  3. #3
    New Lounger
    Join Date
    Mar 2003
    Location
    Frederick, Maryland, USA
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ghost forms (Access 2000)

    It's a self-contained db. And, since I've been backing up everyday, the backup is corrupted too.

    Thanks for the help. I didn't want to hear the answer you gave me, but I guess I know what I'm doing for the next couple of hours.

    <img src=/S/hosed.gif border=0 alt=hosed width=73 height=24> fer shure

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

    Re: ghost forms (Access 2000)

    Check to see what version of VBE6.DLL is on your machine. If it's somewhere around 6.3.91.8, the the problem is caused by a 2002 app installed on the machine. I've seen similar weirdness after an installation of Visio 2002 on a machine with Office 2k SR-1. The cure for the problem, it that's it, is to install SR-3. It won't recover your corrupted databases, but it will prevent it from happening again.
    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
  •