Error using older application in 2007

[vtj]

In trying to use an older database (97) on Access 2007 several tables and
queries are not useable. The error shown is " is not a valid name. Make
sure that it does not include invalid character or punctuation and that it is
not too long. I am thinking that it might have something to do with the
application. It started in Access 97, was converted to Access 2000 and then
converted into Access 2007. I have build a query that produces the same SQL
which will give the same error. The table MSysCompactError has the following
AccessError(-2001) which is an Application-defined or object-defined error.
But that has not helped getting the applicaction to run. Any suggestions?

 

[vtj]

The backups have the same problem even if left as .mdb files. I was hoping
that the compact error might shed some light on why it would not run in
Access 2007. The fact that 2007 build the same SQL for the query is what
lead me to think it has something to do with the application as oppossed to a
specific query. Unfortunately we do not have an old 2000 version operating
any more.

 

[Nicholas Meyer]

hmmm intresting

 

[Stuart Bratesman]

The error message,

" is not a valid name

results from a bug that often occurs in Access 2007 when a user tries to
delete a linked table, or when a user tries to view a query in Design Mode if
the query is based on one or more linked tables. The error message is more
likely to occur when one is linking to a table that resides in an Access
database that is protected by user-level security. It does not matter
whether or not the database in current use employs user-level security or
not. In addition, the appearance of the error message has nothing to do with
the name of the table or the name of any fields within the table.

I have frequently experienced this problem in .mdb files. Others have
experienced the same bug when using the newer .accdb format.

--
Stuart Bratesman, Jr., MPP
Muskie School of Public Service
Univ. of Southern Maine
Portland, Maine

You should create a new db file and import all the objects that work
correctly into it and try to compact it. Any object that doesn't work (like
the query that tells you " is not a valid name) needs to be fixed before
being imported or else recreated in the new db.

Chris
Microsoft MVP

The entry in the MSysCompactError table means you have an
incomplete/corrupted copy of the original db file. If your backups are
corrupted too, you'll have to recreate the missing objects and data.

Chris
Microsoft MVP

The backups have the same problem even if left as .mdb files. I was hoping
that the compact error might shed some light on why it would not run in

[quoted text clipped - 5 lines]

The MSysCompactError table is created when a compaction fails. Revert to a
backup (or compare the db with a good backup) to ensure you haven't lost