RE: " is not a valid name

Sharon,

I have frequently experienced the same

" is not a valid name

problem when using linked tables in Access 2007 (Service Pack 1). The same
bug occurs when you try to delete the table link, making it impossible to
delete the link.

This problem is more likely to occur with the database you are linking to,
the database in which the original table resides, is protected by user-level
security, although others have reported the same problem in instances where
user-level security is not in use.

You may want to report your own experience to the Microsoft Office Feedback
web page found at:

https://feedback.office.microsoft.com/default.aspx?productkey=office2007

I am hoping that if enough people report the problem to Microsoft, they will
then be more likely to investigate and fix it.

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


"Sharon Peterson" wrote:

I have the 60-day trial version of Office 2007 and am having issues with
Access 2007.

When I create (or attempt to modify) queries of tables in a split database I
get the ' " is not a valid name' error message. The query is actually
created, after I clear the error message, and appears to work, but if I try
to re-open it in design view, I can't. In some cases I can open in SQL view,
but sometimes that doesn't work either. I can successfully create the same
query in the backend (i.e. local to the tables).

I've searched all over the web - plenty of people seem to be experiencing
this problem, but there are no real fixes out there. I've checked my
references and tried Autocorrect on and off as suggested in the past.

It seems most of the other people experiencing this are trying to query
Excel or Paradox data. My gut feeling is that the problem is some wonderful
new 'security' feature that's affecting communication between Access and the
data source. Can anyone shed any light on this? Without a solution, I won't
be buying this product when my trial expires.

Thanks,
Sharon
.

Relevant Pages

  • Re: test for empty date
    ... I do not believe my technical advice has been ... I recommend you write a couple of queries to test this. ... returned by the previous query. ... are experiencing something I cannot explain by all my experience with such ...
    (microsoft.public.access.queries)
  • Baffled by access report anomaly displaying data
    ... We're experiencing very strange behavior with an Access 2000 report. ... a query as the recordsource for the report. ... groupings, totals, etc., somewhere along the line the same problem was ...
    (microsoft.public.access.reports)
  • Baffled by access report anomaly displaying data
    ... We're experiencing very strange behavior with an Access 2000 report. ... a query as the recordsource for the report. ... groupings, totals, etc., somewhere along the line the same problem was ...
    (microsoft.public.access.queries)
  • Different wildcard/hyphen behaviour in Windows 2003 Server?
    ... Since several of our clients have migrated to Windows 2003 Server, ... are experiencing different results with queries based on wildcards and ... The query itself resembles ...
    (microsoft.public.inetserver.indexserver)
  • " is not a valid name
    ... get the ' " is not a valid name' error message. ... query in the backend. ... I've searched all over the web - plenty of people seem to be experiencing ... Excel or Paradox data. ...
    (microsoft.public.access.queries)