When I open design view in a query I get "is not a valid name.

[Guest]

I just upgraded to Office 2007 and in one of my database's, when I try to
open my queries in design view, I get this message: "is not a valid name.
Make sure that it does not include invalid characters or punctuation and that
it is not too long.
I have not changed anything in the names of my queries, so I know that they
work, and they work when I open this database on another computer that has
Office 2003. I have already downloaded the patch that let's me be compatible
with older versions, so I'm not sure what is going on.

It let's me run the queries and I can open them in SQL view, just not design
view. I think I must be missing some type of setting, but I'm not sure why
this is the only database out of all the one's that I use that this has
happend to. Please help!

 

[John W. Vinson]

It let's me run the queries and I can open them in SQL view, just not design
view. I think I must be missing some type of setting, but I'm not sure why
this is the only database out of all the one's that I use that this has
happend to. Please help!

Sounds like the database is corrupt - perhaps one of the System tables. Have
you tried Tools... Database Utilities... Compact and Repair?

See the suggestions at http://www.granite.ab.ca/access/corruptmdbs.htm for
other corruption prevention and cure suggestions.

John W. Vinson [MVP]

 

[Guest]

A Union query can only be viewed in SQL view - not design view.

 

[Guest]

You are not alone. It would appear this problem has been going on for a
couple of months. No Union in my queries, so what is going on?

 

[Guest]

Well I am glad that I am not the only one having this problem. I wish they
would figure out how to fix this because I am about to just go back to my
older version. We really rely on access for my job, I have tried the compact
and repair, and I also don't have any union queries, so I just kind of deal
with it for right now.

 

[Guest]

Your post sounds almost identical to mine. This is driving me crazy! I can't
import files from Excel for the same reason. If you find something that works
please let everyone know.

 

[Guest]

Did you ever come across a solution to this problem?

G.

 

[Guest]

I have th same problem.

Did you ever find a solution?

G.

 

[Guest]

No, I haven't. Today I finally just reloaded Access XP and I'll use it until
I hear Micorsoft has fixed the problem. I don't think they really care, to
tell you the truth.

 

[Guest]

I to get this same problem. The queries will run but I cant edit them in
"Design View". I have isoltated the problem to any query with more than one
table defined, i.e A query with a "JOIN". Any query with just a single table
works fine. Problem is my 03 database that I am viewing/editing with 07 has
around 200 queries that have more than one table defined.

What I have found is that if you re-create the query from scratch in 07 the
newly create 07 query works fine. If you then compare the SQL syntax from the
newly created 07 query with the SLQ syntax from the existing 03 query, they
are identical. So it has nothing to do with any SQL syntax incompatibility.

What I find amazing is that surely there are thousands, if not hundreds of
thousands of Access 2007 users by now that would all have come across this
issue, I mean this is not an obscure thing that we are trying to do, yet,
there really isnt much out there if you google it and there isn't anything on
Microsofts Technet.....why?????

BTW, if anyone has figure this out, please let us know.

 

[Guest]

OK, I think I have isolated this even further.

I noticed that I was able to open a query in "Design View" which had
multiple tables in a database which was created in Access 2000-2003 format. I
then twigged to the fact that the database I am have the issue with was
originaly an Access 97 database, which was subsequently converted to
2000-2003 format.

Can anyone else confirm this to be the case with their particular issue?

 

[Guest]

I had begun to wonder if that is one of the reasons I was having the problem,
but one database in particular I just created last year. I did find that if I
un-linked tables and just imported the table into the database I was able to
then view some of the queries in design view, but it did not work for all of
them. I'm like you, there have got to be a multitude of users out there
having the same problem. Microsoft wake up!!
Now about trying to import Excel tables. Do you have a problem there, too?

 

[Guest]

Well, I had no real need as yet to import an excel spreadsheet but I tried it
anyway and guess what????? The error occured.

 

[Guest]

Well, at least I know I am not crazy!

Well, I had no real need as yet to import an excel spreadsheet but I tried it
anyway and guess what????? The error occured.

 

[Guest]

I get exactly the same problem in 2007 when I try to import data from a text
or csv file. It's very annoying. I'm reverting back to 2003 to solve the
problem.

it would be good if Microsoft could do something about it as I am sure there
are a lot of people having this problem.

 

[Guest]

Welcome, Ben to the "Waiting for Microsoft to do something" Club! I too am
back in 2003. I don't have time to go back and "try" to make things work. I
have work to do!

 

[Terri Jones]

If you the tables in the queries are linked to another database or backend database in a mapped drive be careful. If users can create their own map drive letter for the drive location... you will receive the error when attempting to open a query in design view or sql view. It will be appear as if you may have a corrupt file or need to compact/repair the database, but you really need to correct the locations for the linked tables in linked manager in MS Access. So if users can map their own drives and there is no consistency setup of the map drive for each user (ex. K:\Map\ - user 1, and J:\Map\ user 2) then you might want to find an alternative for linking your database tables used in queries to a backend database or another MS Access database.

I just upgraded to Office 2007 and in one of my database's, when I try to
open my queries in design view, I get this message: "is not a valid name.
Make sure that it does not include invalid characters or punctuation and that
it is not too long.
I have not changed anything in the names of my queries, so I know that they
work, and they work when I open this database on another computer that has
Office 2003. I have already downloaded the patch that let's me be compatible
with older versions, so I'm not sure what is going on.

It let's me run the queries and I can open them in SQL view, just not design
view. I think I must be missing some type of setting, but I'm not sure why
this is the only database out of all the one's that I use that this has
happend to. Please help!

06:00 -0700, clopins


Sounds like the database is corrupt - perhaps one of the System tables. Have
you tried Tools... Database Utilities... Compact and Repair?

See the suggestions at http://www.granite.ab.ca/access/corruptmdbs.htm for
other corruption prevention and cure suggestions.

John W. Vinson [MVP]

 

[Terri Jones]

If you the tables in the queries are linked to another database or backend database in a mapped drive be careful. If users can create their own map drive letter for the drive location... you will receive the error when attempting to open a query in design view or sql view. It will be appear as if you may have a corrupt file or need to compact/repair the database, but you really need to correct the locations for the linked tables in linked manager in MS Access. So if users can map their own drives and there is no consistency setup of the map drive for each user (ex. K:\Map\ - user 1, and J:\Map\ user 2) then you might want to find an alternative for linking your database tables used in queries to a backend database or another MS Access database.

I just upgraded to Office 2007 and in one of my database's, when I try to
open my queries in design view, I get this message: "is not a valid name.
Make sure that it does not include invalid characters or punctuation and that
it is not too long.
I have not changed anything in the names of my queries, so I know that they
work, and they work when I open this database on another computer that has
Office 2003. I have already downloaded the patch that let's me be compatible
with older versions, so I'm not sure what is going on.

It let's me run the queries and I can open them in SQL view, just not design
view. I think I must be missing some type of setting, but I'm not sure why
this is the only database out of all the one's that I use that this has
happend to. Please help!

06:00 -0700, clopins


Sounds like the database is corrupt - perhaps one of the System tables. Have
you tried Tools... Database Utilities... Compact and Repair?

See the suggestions at http://www.granite.ab.ca/access/corruptmdbs.htm for
other corruption prevention and cure suggestions.

John W. Vinson [MVP]

 

[John W. Vinson]

If you the tables in the queries are linked to another database or backend database in a mapped drive be careful. If users can create their own map drive letter for the drive location... you will receive the error when attempting to open a query in design view or sql view. It will be appear as if you may have a corrupt file or need to compact/repair the database, but you really need to correct the locations for the linked tables in linked manager in MS Access. So if users can map their own drives and there is no consistency setup of the map drive for each user (ex. K:\Map\ - user 1, and J:\Map\ user 2) then you might want to find an alternative for linking your database tables used in queries to a backend database or another MS Access database.

It's generally a good idea to use the full \\server\path\filename.mdb form for
the linked tables, rather than mapped drives. This isn't susceptible to users
changing their mappings.

To do so you can navigate to the backend via "Network Neighborhood" (or your
operating system's equivalent) rather than "My Computer".
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com