" is not a valid name. Bug in Access 2007

[David P]

I have just installed Office 2007 Professional as an upgrade. Unfortunately
now I am having problems in Access2007.

Firstly, when I try to import either MS Excel files or text files using the
wizard under the External Data tab, it goes right up to the save table step
and then gives me 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.

Well I'm sure there are no invalid characters in any of the field names nor
in the tables themselves. It happens with all of my databases even if I
convert them to Access2007 format.

I sometimes get the same error message when I try to run, open some queries.

I see from a web search that other users have had the same problem but I
don't see any solutions.

Can anyone help?

 

[Allen Browne]

David, have you applied SP1 since installing Office 2007?
If not, you *really* need do to so.
Can't promise for this particular one, but it does address many bugs.

Get the SP from:
http://office.microsoft.com/search/redir.aspx?AssetID=DC102486291033&Origin=HH102511011033&CTT=5

More general info on adapting to A2007:
http://allenbrowne.com/Access2007.html

 

[David P]

Yes I installed SP1 as one of the first steps once I experienced problems.
I'm not sure that the installation worked but it shows SP1 MBO
(12-0-6213.1000) in the about Microsoft Office Access 2007 box.

 

[Allen Browne]

Okay, something else must be going on here.

Have you told Access that the database folder is a trusted location:
Office Button | Access Options | Trust Center | Trust Center Settings

Does it make any difference what folder these files are in? For example in
Vista, some folders are virtualized, so I wonder if that could have it
confused. On Vista, you might also want to create a shortcut to
msaccess.exe, and check the RunAsAdministrator box for the shortcut. Then
start it from there. Just to see if permissions make a difference.

 

[Tom Wickerath]

Hi David,

Check for a reference marked as MISSING. Seems like some folks have Access
applications (2003 and prior) include a reference set to Utility.mda. This
reference is not even available in Access 2007, so it causes a problem when
missing. Here are two very good articles on the subject of missing references:

Solving Problems with Library References (Allen Browne)
http://allenbrowne.com/ser-38.html

Access Reference Problems (Doug Steele)
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html


If that does not work, I would try creating a new blank database in Access
2007, and then import all objects from your source database into the new
database. You shouldn't *have* to do this, but...


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[David P]

Many Thanks Tom and Allen, I tried all of your suggestions but the only one
that has worked is to create a blank database and repopulate it. While this
creates a lot of work, it does give me an oportunity to clean up all the
unnecessary tables that seem to pile up.

 

[Allen Browne]

Okay, that's a good workaround.

You might also like to keep in mind that:
- turning Name AutoCorrect off is a good idea:
http://allenbrowne.com/bug-03.html

- Decompile can be useful, esp.when switching versions.

 

[Jose Juan]

Many Thanks Tom and Allen, I tried all of your suggestions but the only
one
that has worked is to create a blank database and repopulate it. While
this
creates a lot of work, it does give me an oportunity to clean up all the
unnecessary tables that seem to pile up.

 

[ELMAILHETTRICK]

 

[Elaine]

I ran across this same exact error. We found that if you use or have set up
"relationships" between your tables but you can't see the design view of any
queries that have two or more tables without getting the error, a refresh of
your table links fixes the problem.

I had made sure that the references were fine, then disabled auto joins as
my relationship table is already set up and populates, then tried 'refresh
table links', that fixed the problem.

Elaine

 

[TT]

I have struggled with the same issue for weeks. Queries would run fine,
everything appears linked correct, but get the " is not a valid name when
trying to go into design view. Only way I was able to resolve was to move my
linked Databases to my C: drive from my D: drive.

 

[Jared]

Hi All,

Had exactly the same error for over a week, thought it was because I was
working on a mdb i created in 2003 that I was on working on in 2007.
Compacted & Repaired, decompiled, pulled objects into a new db, ran SP2,
yelled kicked & screamed..... no luck.

The " is not a valid table name appeared every time I tried to build a
query, either as an object or embedded behind a form or report.

Then I realised the issue didn't happen if i created a query in the back end.
I got the same error when trying to delete linked tables from the front end.

Found the (stupid mistake) problem to be with the location of the linked
back end. It was in a folder with a ' in the folder name.

I renamed the folder, but unfortunately still couldn't delete the linked
table from the front end. Created a fresh db and imported all objects into it
to get around it. Problem fixed.

So basically, don't have folder names that contain back end files contain a '

jared
www.easytouse.com.au