Can't open DB because of corrupt VB project

I have recently started having trouble with a database in Access 2000.
The problems seem to have started right after I upgraded to Service
Pack 1a. When I try to open the database, I get a message saying, "The
Visual Basic for Applications project in the database is corrupt."
After I click OK--that is the only choice, even though it is not
OK!--I get another message saying, "The form name 'Switchboard' is
misspelled or refers to a form that does not exist." I know that I
have not done anything to modify the switchboard. When I click OK
again I just get more of the first message.

I cannot open the database to try to fix it, or even exit the program
because the error message is always on top. All I can do is click OK,
and the message immediately comes back. In the end I have to do a
Ctrl-Alt-Del to exit the program. I have tried compacting and
repairing the database, but the problem remains.

Is there any way I can get into the VB to try to fix this problem, or
do I have to start over and re-create the database from scratch?

Thanks,
Cliff Lewis

Create a new, empty database and try importing all the objects from the old
database into the new one.

--

Ken Snell
MS ACCESS MVP

"Clifford F. Lewis" wrote in message
...
I have recently started having trouble with a database in Access 2000.
The problems seem to have started right after I upgraded to Service
Pack 1a. When I try to open the database, I get a message saying, "The
Visual Basic for Applications project in the database is corrupt."
After I click OK--that is the only choice, even though it is not
OK!--I get another message saying, "The form name 'Switchboard' is
misspelled or refers to a form that does not exist." I know that I
have not done anything to modify the switchboard. When I click OK
again I just get more of the first message.

I cannot open the database to try to fix it, or even exit the program
because the error message is always on top. All I can do is click OK,
and the message immediately comes back. In the end I have to do a
Ctrl-Alt-Del to exit the program. I have tried compacting and
repairing the database, but the problem remains.

Is there any way I can get into the VB to try to fix this problem, or
do I have to start over and re-create the database from scratch?

Thanks,
Cliff Lewis

I get the same message if I try to use File-Get External
Data-Import.... I am able to import the tables into Excel using Get
External Data, but that is a lot of work, does not include the
functionality of the old database, and includes fields that I do not
recognize, such as s_Generation and s_GUID.

On Mon, 6 Sep 2004 15:32:18 -0400, "Ken Snell [MVP]"
wrote:

Create a new, empty database and try importing all the objects from the old
database into the new one.

On Wed, 08 Sep 2004 17:09:44 -0400, Clifford F. Lewis
wrote:

I get the same message if I try to use File-Get External
Data-Import.... I am able to import the tables into Excel using Get
External Data, but that is a lot of work, does not include the
functionality of the old database, and includes fields that I do not
recognize, such as s_Generation and s_GUID.

The functionality will only exist if you import into Access instead of
into Excel; and of course you'll need to import the Forms, Queries,
Reports, Modules and Macros (if any) as well as the data.

The fields s_Generation and s_GUID are generated automatically when
you Replicate the database; they keep track of which data has been
replicated and when. If you're importing from a replica which is not
the design master you may be digging yourself into a hole!

John W. Vinson[MVP]
(no longer chatting for now)

I think I am out of luck, because there seems to be no way to import
from my original Access database without using Excel as an
intermediary, unless there is something other than File-Get External
Data-Import.... No matter what I do, I always get the message that
the Visual Basic is corrupted.

As I try to re-create the database, this time I am at least putting
the design master on the system that is backed up daily, instead of in
the briefcase folder on my notebook. I guess I have to chalk it up to
a lesson learned the hard way.

Cliff Lewis

On Wed, 08 Sep 2004 16:07:30 -0600, John Vinson
wrote:

On Wed, 08 Sep 2004 17:09:44 -0400, Clifford F. Lewis
wrote:

I get the same message if I try to use File-Get External
Data-Import.... I am able to import the tables into Excel using Get
External Data, but that is a lot of work, does not include the
functionality of the old database, and includes fields that I do not
recognize, such as s_Generation and s_GUID.

The functionality will only exist if you import into Access instead of
into Excel; and of course you'll need to import the Forms, Queries,
Reports, Modules and Macros (if any) as well as the data.

The fields s_Generation and s_GUID are generated automatically when
you Replicate the database; they keep track of which data has been
replicated and when. If you're importing from a replica which is not
the design master you may be digging yourself into a hole!

John W. Vinson[MVP]
(no longer chatting for now)