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?
-- 
Cheers
David

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

-- 
Allen Browne - Microsoft MVP.  Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"David P" <djpstba@anaddress> wrote in message
news:9E3B4544-9689-47D0-B15C-F3C247CCE813@microsoft.com...
>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?
> -- 
> Cheers
> David 

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.
-- 
Cheers
David


"Allen Browne" wrote:

> 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
> 
> -- 
> Allen Browne - Microsoft MVP.  Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.

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.

-- 
Allen Browne - Microsoft MVP.  Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"David P" <djpstba@anaddress> wrote in message
news:19235EEB-2300-44C3-B8CA-AF605AB5BB9E@microsoft.com...
> 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.
> -- 
> Cheers
> David 

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" wrote:

> 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.
> -- 
> Cheers
> David

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.

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.

-- 
Allen Browne - Microsoft MVP.  Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"David P" <djpstba@anaddress> wrote in message
news:8AB6CE74-7798-4080-B1A2-F10F97C3B806@microsoft.com...
> 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. 

"David P" <djpstba@anaddress> wrote in message 
news:8AB6CE74-7798-4080-B1A2-F10F97C3B806@microsoft.com...
> 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.