Can't access design view

[Don]

I am using Access 2007 and I have a problem that I've never experienced any
any database I've ever constructed.

I have an existing database that I updated to the new 2007 format from 2000.
I can't open half of my queries in design view. I get the following error
message:

" is not a valid name. Make sure that it does not include invalid
characters or punctuation and that it is not too long.

The query is named: qryUNPAID

Can someone give me some direction?

 

[Jerry Whittle]

First make a copy of the database file and put away for safe keeping.

Next run a compact and repair. See if that fixes it.

If not try creating a new database file and importing everything from the
backup copy to the new database file.

 

[Don]

Thank you for your suggestions--I was hoping they would work. I tried both
ideas and neither corrected the problem. If you have any other ideas, I'd
love to hear them because I'm at a loss as to what to do. I certainly don't
want to have to rebuild this database from scratch; it's 3 or 4 years old and
I can't remember everything that went into it.

 

[Klatuu]

Have you downloaded and installed SP1 for Office 2007?

 

[Don]

Yes, this query is linked to tables in another database. The database sits
on my company's server. People around the office use the front end database.


Forgive my ignorance, but how do I create a trusted folder?

 

[Don]

I have installed the Window's SP1.

 

[Klatuu]

Can you actually run the query and just not open it in design view?
Have you tried renaming it?

 

[alanwf]

I am using Access 2007 and I have a problem that I've never experienced any
any database I've ever constructed.

I have an existing database that I updated to the new 2007 format from 2000.
I can't open half of my queries in design view. I get the following error
message:

" is not a valid name. Make sure that it does not include invalid
characters or punctuation and that it is not too long.

The query is named: qryUNPAID

Can someone give me some direction?

TRY THIS:

It is not the queries, but the linked tables to a backend mdb file. Steps
that I had to take are:
1. Import all tables in the backend mdb file into a new backend mdb file.
2. The linked tables in the frontend mdb file cannot be deleted. So,
import everything EXCEPT the linked tables into a new frontend mdb file.
3. In the new frontend mdb file, create links to the tables in the new
backend mdb file.

alanwf