Send Access 2007 back to the drawing board

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Today I reloaded Access XP onto my computer. I have had it with Access 2007!
Almost every query in over half my databases cannot be opened in design view!
I get this stupid error message "is not a valid file name. The " is part of
the error message. It doesn't use the name of the query at all. I also have
to copy and paste excel spreadsheets into tables, because it will not allow
me to import excel files for the same reason. I have converted everything to
Access 2007 format and Excel 2007 format. I have compacted and repaired every
single database. I have done everything I can think of to solve this problem
and nothing works! I have read posts about this problem, but no solutions. Is
Microsoft even aware that this is going on. I have never been this frustrated
with software before! If anyone knows what is going on, please clue the rest
of us in!

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-a3f1-916c38d108bf&dg=microsoft.public.access
 
A man called r Brick had a firm in the land of Far Away that made bricks.
Every now and again they would improve their bricks and make them more
versatile so that people with a little training could construct very nice
walls and houses. Some people who were experts were able to construct all
types of things. Everyone was happy in the land of Far Away

But what if, thought Mr Brick, we could make a brand new brick that would be
so clever that anyone, even those without any training, could at least make a
wall that would look the part, even if it wasn’t that strong. It will not
matter as most people just want a wall to stand up they don’t need it to
actually “do†anything like hold up a roof.

So Mr Brick tried very hard to make his wonderful new brick. But alas it
would not work and the research was very expensive. Walls lasted a short
while then fell over. Some people – the ones who had been expert with the
old brick, were in fact able to make strong walls with the new type of brick.
Well though Mr Brick, here s a great idea, we will sell our new brick to lot
of people and they will tell us what is wrong with them, “they†can do our
research for us – for free, and here is the best bit he thought – they will
pay us to do it for us. We can then put out a few improvements that people
can use to make the bricks do what they thought they would in the first
place. And so he started to sell his new Wonder Brick.

Of course they didn’t work very well but it didn’t matter because everyone
who’s wall fell down thought they had built it wrong an it was their fault,
and if only they tried harder everything would be OK. Only Mr Brick new that
it was really the bricks that didn’t work and sooner or later everyone would
realise this. As long as enough people told him of their problems he would
have enough free research to “finally†create a brick that would do the job
it was intended for.
 
Are the query names greater than 64 characters long? AC2007 will not allow
you to create objects with names > 64 characters. I don't know what happens
if you convert long names from a previous version...

UpRider
 
Today I reloaded Access XP onto my computer. I have had it with Access 2007!
Almost every query in over half my databases cannot be opened in design view!
Click to expand...

Going on the face value of your statement, I would guess that Access
2007 is not happy on your machine. I haven't used 2007 extensively,
but so far have not seen this happen.

Office Suites and Versions when you install "in place" over an older
one or mix versions etc... have been known to break badly.
Access 2007 format and Excel 2007 format. I have compacted and repaired every
single database. I have done everything I can think of to solve this problem
and nothing works! I have read posts about this problem, but no solutions. Is
Click to expand...

I would guess from what you say, that this is not a problem with your
files, it is a problem with the Office installation not working
properly on your PC.
Microsoft even aware that this is going on. I have never been this frustrated
with software before! If anyone knows what is going on, please clue the rest
of us in!
Click to expand...

Have you tried your data files on another machine, preferably one that
has little history of use and only has Office 2007 on it and no
previous versions?

If your machine is modern and has lots of RAM, you could try running
VirtualPC and a readymade trial Office 2007 vhd and see whether there
is a machine specific problem.

HTH
Ananda
 
I'm afraid all the machines in our area are the same age and have had the
same versions of Office on them.
 
I'm afraid all the machines in our area are the same age and have had the
same versions of Office on them.
Click to expand...

Then this is an impasse. I can only tell you that I haven't
encountered the extent of the problems that you are facing. To prove
or disprove the idea that Access 2007 will work properly when it is
comfortably seated, you will need to find someone who has a different
machine (history).

Best wishes

Ananda
 
I don't know if anyone has suggested this but have you making sure the palce
you put the datanase you alos placed as in the Trusted Loactions? Access
2007 will not run code or much of anything for that matter if it's not.
 
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
 
I too shared with your frustration with these importing errors.

What I found was the case for me, was that Access 2007 has more integrity
rules, checks, etc . that it goes through.

The reason I got the ' is part of the error message was because one of my
linked tables had a file path that included an apostrophe. It wasn't the
table I was importing into, just a linked table in the database. By fixing
the file folder name (remove apostrophe) I was able to get past this error
message.
 
Back
Top