IE7 broke my network. (.mdb files etc.)

  • Thread starter Thread starter GSV Three Minds in a Can
  • Start date Start date
G

GSV Three Minds in a Can

I foolishly installed the IE7 upgrade on several PCs. Now when I try to
update an Access database across the network I get all sorts of foolish
'open file' security error messages about unknown publisher, and (if I
persist) Access declines to run the files, claiming it's not on my
Intranet or a trusted site.

A quick look at 'my network places' reveals that, yea verily, all the
other PCs are now 'Internet' devices instead of local network. Open IE7
security, and check, and I do have 'UNC paths' box ticked, and/or the
'discover intranet automatically'. Doesn't happen .. have to actually
enter the PC names for the other PCs into the 'exceptions' box manually.

At that point 'my network places' admits they are on local network
again, and Access can open them (they were being =reached= locally all
the time, even if my ADSL connection was offline).

=======================================================
Come on M$, this is cr&p, don't you beta test releases any more?? And
why has IE7 got it's sticky fingers in simple file access across the
network. And why is MS Access mega-paranoid about opening a remote
database when .jpg, .doc, etc open just fine??
=======================================================
 
Why don't you post your inquiry in the correct newsgroup relative to IE7?
http://www.microsoft.com/windowsxp/...indows.inetexplorer.ie6.browser&lang=en&cr=US

--
Carey Frisch
Microsoft MVP
Windows Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/


---------------------------------------------------------------------------

:

| I foolishly installed the IE7 upgrade on several PCs. Now when I try to
| update an Access database across the network I get all sorts of foolish
| 'open file' security error messages about unknown publisher, and (if I
| persist) Access declines to run the files, claiming it's not on my
| Intranet or a trusted site.
|
| A quick look at 'my network places' reveals that, yea verily, all the
| other PCs are now 'Internet' devices instead of local network. Open IE7
| security, and check, and I do have 'UNC paths' box ticked, and/or the
| 'discover intranet automatically'. Doesn't happen .. have to actually
| enter the PC names for the other PCs into the 'exceptions' box manually.
|
| At that point 'my network places' admits they are on local network
| again, and Access can open them (they were being =reached= locally all
| the time, even if my ADSL connection was offline).
|
| =======================================================
| Come on M$, this is cr&p, don't you beta test releases any more?? And
| why has IE7 got it's sticky fingers in simple file access across the
| network. And why is MS Access mega-paranoid about opening a remote
| database when .jpg, .doc, etc open just fine??
| =======================================================
|
| --
| GSV Three Minds in a Can
| 7,053 Km walked. 1,267Km PROWs surveyed. 23.0% complete.
 
I foolishly installed the IE7 upgrade on several PCs. Now when I try to
update an Access database across the network I get all sorts of foolish
'open file' security error messages about unknown publisher, and (if I
persist) Access declines to run the files, claiming it's not on my Intranet
or a trusted site.

A quick look at 'my network places' reveals that, yea verily, all the
other PCs are now 'Internet' devices instead of local network. Open IE7
security, and check, and I do have 'UNC paths' box ticked, and/or the
'discover intranet automatically'. Doesn't happen .. have to actually
enter the PC names for the other PCs into the 'exceptions' box manually.

At that point 'my network places' admits they are on local network again,
and Access can open them (they were being =reached= locally all the time,
even if my ADSL connection was offline).

<snip>

IE7 questions should be asked in the Internet Explorer newsgroup. There are
quite a few posts there so peruse them for something on topic before posting
a new message.

Newsreader:
news://msnews.microsoft.com/microsoft.public.internetexplorer.general

On the Web:
http://www.microsoft.com/communitie...?dg=microsoft.public.internetexplorer.general

Release Notes
http://msdn2.microsoft.com/ie/Aa740486
 
GSV said:
I foolishly installed the IE7 upgrade on several PCs. Now when I try to
update an Access database across the network I get all sorts of foolish
'open file' security error messages about unknown publisher, and (if I
persist) Access declines to run the files, claiming it's not on my
Intranet or a trusted site.

A quick look at 'my network places' reveals that, yea verily, all the
other PCs are now 'Internet' devices instead of local network. Open IE7
security, and check, and I do have 'UNC paths' box ticked, and/or the
'discover intranet automatically'. Doesn't happen .. have to actually
enter the PC names for the other PCs into the 'exceptions' box manually.

At that point 'my network places' admits they are on local network
again, and Access can open them (they were being =reached= locally all
the time, even if my ADSL connection was offline).

=======================================================
Come on M$, this is cr&p, don't you beta test releases any more?? And
why has IE7 got it's sticky fingers in simple file access across the
network. And why is MS Access mega-paranoid about opening a remote
database when .jpg, .doc, etc open just fine??
=======================================================

I have to agree that IE7 is a near-total disaster.

Every machine here that it's installed on (i.e. every machine that's
been booted up in the last week and accepted "updates") is suffering
from some sort of problem since the IE7 update.

I also have to wonder about the testing methods employed by microsoft.

I do like the tabbing feature of IE7, but it hogs memory and often
brings the system to a halt (dual core AMD XP4800+) when there are
multiple windows open.

It doesn't get on well with anti-spyware programs.

It sucks.

I wonder if it has "ulterier motives" attached?



Odie
 
from the wonderful said:
<snip>

IE7 questions should be asked in the Internet Explorer newsgroup.

It wasn't a question, it was a complaint, comment, etc. and the problem
does NOT show up in IE7, it shows up in MS Access, when trying to open a
file across a (local!) network. In fact it show up in 'my network
places', since all 'local network' nodes/resources now show up as
'Internet'.
 
from the wonderful said:
Why don't you post your inquiry in the correct newsgroup relative to IE7?
http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?dg=
microsoft.public.windows.inetexplorer.ie6.browser&lang=en&cr=US

For the same reason you choose to top-post with a .sigsep which deletes
everything you are quoting when someone responds??

Besides, it wasn't a query, it was a complaint. And what is broken is
'my network places', which SHOULD have little or nothing to do with IE7
(I suspect people getting the sort of errors I was seeing would be
pretty unlikely to go looking in the guts of IE7 'security tab' to find
the culprit).
 
Rock said

It wasn't a question, it was a complaint, comment, etc. and the problem
does NOT show up in IE7, it shows up in MS Access, when trying to open a
file across a (local!) network. In fact it show up in 'my network places',
since all 'local network' nodes/resources now show up as 'Internet'.

It it's a result of the IE7 install, that should be posted to the IE7
newsgroup. Actually in this case maybe crossposting to both
windowsxp.general and internet explorer newsgroups would have been the way
to go, but the internet explorer newsgroup should have been included.
 
GSV Three Minds in a Can said:
Come on M$, this is cr&p, don't you beta test releases any more??

M$ expect their users to do the beta testing for them, so your
experience comes as no surprise. ("It compiles? Ship it!")

Don't touch Fister until *at least* SP1 comes out for it.
 
Rock said:
It it's a result of the IE7 install, that should be posted to the IE7
newsgroup. Actually in this case maybe crossposting to both
windowsxp.general and internet explorer newsgroups would have been the
way to go, but the internet explorer newsgroup should have been included.

And an Access newsgroup too :-)

They would have said to use a front end mdb (forms, code, etc) on the
local drive with linked tables to the data mdb on the network.
 
from the wonderful said:
And an Access newsgroup too :-)

They would have said to use a front end mdb (forms, code, etc) on the
local drive with linked tables to the data mdb on the network.

Yeah right, that's a recipe for total confusion and utter disaster,
since you have to keep the 'front end' copies consistent on all the
different machines.

I'd still like to know why Access is so paranoid about a remote
database, whereas excel(?), word etc. have no problem opening a remote
file, which could be equally stuffed full of wicked VBA code.
 
Trevor Best said:
included.

And an Access newsgroup too :-)

They would have said to use a front end mdb (forms, code, etc) on the
local drive with linked tables to the data mdb on the network.

BS. The OP should NOT have to re-write his app just so
a piss-poor MS update can function. Totally unacceptable.
 
GSV Three Minds in a Can writes


M$ expect their users to do the beta testing for them, so your
experience comes as no surprise. ("It compiles? Ship it!")

Don't touch Fister until *at least* SP1 comes out for it.

Anyone who uses the M$ designation or b*stardizes a name shows how juvenile
and lacking in credibility they are. I run Vista RTM Ultimate - in fact
this message is being composed in Windows Mail on it. It runs great.
 
Anyone who uses the M$ designation or b*stardizes a name shows how juvenile
and lacking in credibility they are.

Heh. You should take a peek into alt.sysadmin.recovery sometimes, see
what _they_ call the cumbersome monstrosities that they have to look
after. That's the people who run your network...

Some people bastardise because they're puerile. Others bastardise
because they _know_. Being able to tell the difference can be
important.

Cheers - Jaimie
--
So, what do *you* do for a living?
I sit in a chair pressing small plastic rectangles with my fingers
while peering at many tiny, colored dots. -- Peter Manders
 
"Rock"
wrote:

Heh. You should take a peek into alt.sysadmin.recovery sometimes, see
what _they_ call the cumbersome monstrosities that they have to look
after. That's the people who run your network...

Some people bastardise because they're puerile. Others bastardise
because they _know_. Being able to tell the difference can be
important.

If someone truly knows and is not juvenile they wouldn't play little games
like that. I was in the Techbeta and have used Vista from the beginning. I
know about it good points and bad points.
 
If someone truly knows and is not juvenile they wouldn't play little games
like that.

Technical computer professionals tend to juvenile jokes as a coping
mechanism. Same way as hospital staff use black humour.
I was in the Techbeta and have used Vista from the beginning. I
know about it good points and bad points.

Congratulations. I spent a week with each of the last couple of RC's
and am therefore skipping it at least until SP1. I have no need to
know it for work, and no need at all to use it at home.

Cheers - Jaimie
 
Rock said:
Anyone who uses the M$ designation or b*stardizes a name shows how
juvenile and lacking in credibility they are.

OTOH, it might be argued that anyone who doesn't do so shows how they lack
any clue.
 
OTOH, it might be argued that anyone who doesn't do so shows how they lack
any clue.

One can argue anything. You didn't ..does that mean you have no clue? I
have first hand experience with Vista. I stand by what I said...using M$ or
b*stardizing a name is just plain juvenile.
 
from the wonderful said:
Anyone who uses the M$ designation or b*stardizes a name shows how
juvenile and lacking in credibility they are. I run Vista RTM Ultimate
- in fact this message is being composed in Windows Mail on it. It
runs great.

Thereby demonstrating you are a great/perfect customer, but a lousy
tester. I can't comment on Vista, it's go nothing in it I want or need,
but every other M$ product I've ever been involved with beta testing has
gone to release with PLENTY of known bugs left in.

As to acronyms, I personally use "M$" because when I complain about/to
an entity real often I like a nice short acronym to use. MS is already
taken (on several counts), M$ works just fine - everyone knows exactly
whom I mean. Yep, even twits like you.
 
"GSV Three Minds in a Can"wrote
Rock said

Thereby demonstrating you are a great/perfect customer, but a lousy
tester. I can't comment on Vista, it's go nothing in it I want or need,
but every other M$ product I've ever been involved with beta testing has
gone to release with PLENTY of known bugs left in.

As to acronyms, I personally use "M$" because when I complain about/to an
entity real often I like a nice short acronym to use. MS is already taken
(on several counts), M$ works just fine - everyone knows exactly whom I
mean. Yep, even twits like you.

Never said Vista doesn't have any bugs, but it does run great on this
system. Are you running it? Were you in the TechBeta? Were you in the
beta newsgroups? All software has bugs, no matter how long it's been
available. I took exception to the blanket statement that Vista is of no
value until after SP1. That's the standard statement from someone who has
no experience with a product. It's just bashing or passing on what they
heard someone else mouth.

Resorting to name calling is the province of the weak.
 
Rock said:
I run Vista RTM Ultimate - in fact
this message is being composed in Windows Mail on it. It runs great.

I pity you. I suppose you're an MCSE (Must Ask Someone Else) as well?

ps. the Ford Edsel and Pinto "ran great" too.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top