A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Access 2007 - Query Design View Error - " is not a valid name...



 
 
Thread Tools Display Modes
  #1  
Old October 29th, 2008, 06:26 PM posted to microsoft.public.access
emc
external usenet poster
 
Posts: 34
Default Access 2007 - Query Design View Error - " is not a valid name...

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!
  #2  
Old October 29th, 2008, 10:41 PM posted to microsoft.public.access
ntc
external usenet poster
 
Posts: 130
Default Access 2007 - Query Design View Error - " is not a valid name...

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #3  
Old October 30th, 2008, 03:26 AM posted to microsoft.public.access
Bronwyn
external usenet poster
 
Posts: 7
Default Access 2007 - Query Design View Error - " is not a valid name.

We have experienced the same thing on a number of our databases. When you
right click and go to "Open in design view" it will bail out to SQL view
(sometimes).

I'd love to hear if there's a fix for it though!

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #4  
Old October 30th, 2008, 01:06 PM posted to microsoft.public.access
ntc
external usenet poster
 
Posts: 130
Default Access 2007 - Query Design View Error - " is not a valid name.

a query will go direct to SQL view if the sql statement is too complex for a
design grid visual representation.

there is nothing wrong in a case like this (presuming your query and
forms/reports are working of course....) there are plenty of sql statements
particularly involving joins of one table on itself that can not be displayed
via grid....

"Bronwyn" wrote:

We have experienced the same thing on a number of our databases. When you
right click and go to "Open in design view" it will bail out to SQL view
(sometimes).

I'd love to hear if there's a fix for it though!

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #5  
Old October 30th, 2008, 10:07 PM posted to microsoft.public.access
Bronwyn
external usenet poster
 
Posts: 7
Default Access 2007 - Query Design View Error - " is not a valid name.

But why would it display fine in Access 2003 and not in 2007? If I open up
the database in 2003 it will display fine in grid view but won't display in
2007.

"NTC" wrote:

a query will go direct to SQL view if the sql statement is too complex for a
design grid visual representation.

there is nothing wrong in a case like this (presuming your query and
forms/reports are working of course....) there are plenty of sql statements
particularly involving joins of one table on itself that can not be displayed
via grid....

"Bronwyn" wrote:

We have experienced the same thing on a number of our databases. When you
right click and go to "Open in design view" it will bail out to SQL view
(sometimes).

I'd love to hear if there's a fix for it though!

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #6  
Old October 30th, 2008, 10:58 PM posted to microsoft.public.access
ntc
external usenet poster
 
Posts: 130
Default Access 2007 - Query Design View Error - " is not a valid name.

don't know

I suppose you could copy that sql code into a brand new query, run it, and
see if it will display the design grid or not....just a possibility....



"Bronwyn" wrote:

But why would it display fine in Access 2003 and not in 2007? If I open up
the database in 2003 it will display fine in grid view but won't display in
2007.

"NTC" wrote:

a query will go direct to SQL view if the sql statement is too complex for a
design grid visual representation.

there is nothing wrong in a case like this (presuming your query and
forms/reports are working of course....) there are plenty of sql statements
particularly involving joins of one table on itself that can not be displayed
via grid....

"Bronwyn" wrote:

We have experienced the same thing on a number of our databases. When you
right click and go to "Open in design view" it will bail out to SQL view
(sometimes).

I'd love to hear if there's a fix for it though!

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #7  
Old November 3rd, 2008, 03:38 PM posted to microsoft.public.access
emc
external usenet poster
 
Posts: 34
Default Access 2007 - Query Design View Error - " is not a valid name.

My queries are quite simple and I have never had a problem working in 2003.
This is totally a bug in 2007.

To open any query in SQL view, select the query, go to the Home tab on the
Ribbon and the first button is called View, select SQL from the list. I can
also open in Datasheet view, in other words the query will run fine. I can
also open all tables in any view as well.

This is a known bug but there is no fix. I can open any single-table query
in design view, just not a query based on 2 or more tables. This issue has to
do with joins, since I also encounter the same error when attempting to open
the Relationship window.

"NTC" wrote:

don't know

I suppose you could copy that sql code into a brand new query, run it, and
see if it will display the design grid or not....just a possibility....



"Bronwyn" wrote:

But why would it display fine in Access 2003 and not in 2007? If I open up
the database in 2003 it will display fine in grid view but won't display in
2007.

"NTC" wrote:

a query will go direct to SQL view if the sql statement is too complex for a
design grid visual representation.

there is nothing wrong in a case like this (presuming your query and
forms/reports are working of course....) there are plenty of sql statements
particularly involving joins of one table on itself that can not be displayed
via grid....

"Bronwyn" wrote:

We have experienced the same thing on a number of our databases. When you
right click and go to "Open in design view" it will bail out to SQL view
(sometimes).

I'd love to hear if there's a fix for it though!

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #8  
Old November 3rd, 2008, 03:40 PM posted to microsoft.public.access
emc
external usenet poster
 
Posts: 34
Default Access 2007 - Query Design View Error - " is not a valid name.

You simply go to the Home tab and select View from the Ribbon and choose SQL.
How do I setup a network backend as a trusted location?

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #9  
Old November 3rd, 2008, 03:41 PM posted to microsoft.public.access
emc
external usenet poster
 
Posts: 34
Default Access 2007 - Query Design View Error - " is not a valid name.

My queries are rather simple. Two tables, inner join, based on less than 10
fields.
My database works fine in 2003, it's a 2007 bug.

"NTC" wrote:

a query will go direct to SQL view if the sql statement is too complex for a
design grid visual representation.

there is nothing wrong in a case like this (presuming your query and
forms/reports are working of course....) there are plenty of sql statements
particularly involving joins of one table on itself that can not be displayed
via grid....

"Bronwyn" wrote:

We have experienced the same thing on a number of our databases. When you
right click and go to "Open in design view" it will bail out to SQL view
(sometimes).

I'd love to hear if there's a fix for it though!

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

  #10  
Old November 3rd, 2008, 03:45 PM posted to microsoft.public.access
emc
external usenet poster
 
Posts: 34
Default Access 2007 - Query Design View Error - " is not a valid name.

You can also get to SQL View by opening the Query in datasheet view (running
the query) and go to View on the menu and SQL will be listed there.

"NTC" wrote:

you are able to: "run my queries or view them in SQL"

but not view them in design view??

how do you get to view the sql if you can not open them in design view?

have you established the backend file as a Trust Location?

"emc" wrote:

My database was built in 2003 and runs great in 2003, however, I get this
error when attempting to open a query in design view within Access 2007 (" is
not a valid name...).

I am running Office Professional Pro 2007 with SP1 on Win XP SP2.

All of my tables are linked to a backend Access DB on our network.
I generate this error attempting to view queries containing 2 or more tables.
I also generate this error attempting to view the Relationships window.

I have used proper naming conventions, no punctuation marks, etc. I am able
to open my tables in either view as well as run my queries or view them in
SQL. Also, I do not have security applied to this MDB.

Upon calling Microsoft, they apparently have listed this item as a bug (ref
#37769) but I haven't seen a fix anywhere yet.

Anyone hear of anything?

Thx!

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 06:04 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.