Oh, I like Vista, don't get me wrong. Now that I'm used to it and have found
where they've hidden everything, I like it at least as much as I did XP,
maybe more. I have Vista Ultimate on two desktop boxes and on one laptop.
But the niceties of Vista don't excuse the whole concept of the UAC, which
by all measures of look-and-feel seems to have been tacked on to the system
almost as an afterthought. Having to confirm nearly any significant
operation with a message box just doesn't cut it as a well thought out
strategy for dealing with security. Yes, I know there are many other
security mechanisms at work, but the popup UAC serves more to annoy the
users than prevent nefarious code from screwing with the machine. It pops up
so often that users will automatically react by allowing the operation
without even paying attention to what that operation is and what initiated
it. Too many false alarms, in my opinion.
There are some very smart people at MS -- they could have done better than
the UAC.
--
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)
"Gary Keramidas" <GKeramidasATmsn.com wrote in message
...
i was and still am on the vista beta team. i complained about a lot of
things, but the only thing they relented on was giving us back list view in
explorer. otherwise, that would be gone, too.
there a things that just take more clicks to do in vista, than in xp,
changing the time, getting to the nic properties, etc. couple that with
the uac prompts and it's downright annoying. first thing i do is go into
the group policy editor and turn it all off. i don't use the interface in
the user cpl applet.
there are some pretty cool things in vista that a lot of people don't know
about, but probably wouldn't care about unless they're really into
computers. all the diagnostic history, the task scheduler and the event
reporting system. but i think a lot of it at a performance cost, too.
sorry for the off topic post, but just thought i throw this out.
--
Gary
"Chip Pearson" wrote in message
...
I suppose, begrudgingly, it's best to turn it back on when done.
The first thing I did after installing Vista was to turn off the UAC. It
is a kludge solution to security, and it displays itself so often, users
reactively click "Continue" without even reading what action is being
approved. The boy who cried wolf and all that. The UAC is one of the
dumber things to come out of Microsoft in quite some time.
--
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)
"Peter T" <peter_t@discussions wrote in message
...
Also, in Vista you may need to turn off UAC (User Account Control). At
least
that's the only way I can get RegSvr32 to work in Vista, though I'd be
very
interested to know otherwise.
Search "UAC" in Vista help to get to lead you there.
I suppose, begrudgingly, it's best to turn it back on when done.
Regards,
Peter T
"Chip Pearson" wrote in message
...
You need to register the DLL with RegSv32. From the Run dialog on the
Windows Start menu, enter
RegSvr32 "C:\Path\FileName.dll"
When you compile an ActiveX DLL in VB6, it is automatically registered
on
that local machine. But when you move it to another machine, you must
RegSvr32 the file.
--
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)
wrote in message
...
On 28 Nov, 19:53, "Gary Keramidas" <GKeramidasATmsn.com wrote:
just a guess, do you have to register the dll?
--
Gary
wrote in message
...
Hi,
I have an add-in that uses a VB6 DLL. It works perfectly in XP
but
when it's in Vista the DLL doesn't link. I put the DLL in the
system32 folder.
Has any else come across this problem know a solution?
Thank you in advance.
Best
Meldrum- Hide quoted text -
- Show quoted text -
Hi Gary,
Thank you for your reply.
I thought about that but I use a XLA (VBA wrapper) to call the DLL
which avoided the hassle of registering the DLL, which did the trick
in 2000 and XP. Is Vista different in that all DLLs need registering
or it is it to do with access rights - just not sure.
Best
Meldrum