"Kevin Provance" <ca***@tpasoft.com> wrote in message
news:%23IJXL8QXHHA.600@TK2MSFTNGP05.phx.gbl...
| This might have already been answered, but I cannot find it.
|
| Using VB6 SP6 under Vista.  I am logged on as an administrator.  When I
| attempt to compile an ActiveX DLL, I get the message "Error accessing
system
| registry"
|
| When I try to register the same DLL I get an error 0x80004005
| DllRegisterServer failed (seems to be another registry access thing).  I
| knew this was going to be a PITA.
|
| Does anyone know what's up with this?  I'll continue to Google in the
| meantime, but there isn't a lot of info out there that I am able to find
as
| of yet.
|
| Thanks guys
|
| - Kev
|
|

"MikeD" <nob***@nowhere.edu> wrote in message
news:OBBYFCTXHHA.1200@TK2MSFTNGP04.phx.gbl...
|
| "Kevin Provance" <ca***@tpasoft.com> wrote in message
| news:udQXAtRXHHA.4872@TK2MSFTNGP03.phx.gbl...
| > Well, apparently if you make VB6.exe and Link.exe at always run as
| > administrator, this will solve some of the problem.
| >
| > What sucks is that I keep all my projects in their own folder, and Vista
| > won't allow VB to write settings to the .vbp file.  Stupid Vista.  Too
| > many
| > workarounds.  :\
|
|
| I don't know much about Vista yet, but from what I can gather from other
| posts and just reading about Vista, try turning off UAC. From my
understand,
| with it own, most programs are going to "think" they're running under
| non-admin accounts....even if you are logged on as an administrator.  To
me,
| this is no different than people trying to run VB (or any development
| programs) under non-admin accounts in earlier versions of Windows.
|
| --
| Mike
| Microsoft MVP Visual Basic
|

"Kevin Provance" <ca***@tpasoft.com> wrote in message
news:Om2H23UXHHA.1388@TK2MSFTNGP05.phx.gbl...
> Well Mike...if you remember, I'm the type of guy who will just forcus on a
> problem until I've got it fixed and everything else be damned (minus my
son,
> of course).  I've been studying Vista all day.  MSDN, newgroups, Google,
you
> name it and I think I'm starting to get a grasp on the monster I am up
> against, and it ain't pretty.
>
> Apparently, running as an Admin or setting a program to run as Admin will
> encourage the UAC prompt, where as running as a standard user won't (ass
> backwards, ain't it?)  The more privlidges you give yourself, the more
> prompts you get.
>
> The biggest problem I've found in my cool little registry hack to register
> and unregister ActX DLLs and OCXs by double-clicking on the given file
won't
> work with Vista because one cannot set regsvr32 to run ad admin.  The file
> prevents it (hard coded that way I am guessing).  So, to properly register
> all the ActX stuff requires loading it up and compiling...which becomes
> tedious after awhile.  Because I keep all my code on the XP box and load
my
> code via the network I had to set sharing privlidges on XP to accomodate
the
> Vista box.  I'd hate to have to have two separate code bases, one on each
> box to work off of, so for now that's how I'm doing it.
>
> Try reading the Vista newsgroups....lots of complaining about the UAC.
> Ultimately I will shut it off, but for now I am running with the least
> privlidges as to ensure a properly running program as most users will
> ultimately be running the same.  Provided things go well under those
> settings, being an Admin should be a breeze.
>
> So yeah, Vista is really picking about ActiveX, registry writing and file
> writing.  The Developer Best Practices and Guidelines for Applications in
a
> Least Privileged Environment artivle is a real help and worth reading.
:-)
>
> - Kev
>
> <snipped>

>Try reading the Vista newsgroups....lots of complaining about the UAC.
>Ultimately I will shut it off, but for now I am running with the least
>privlidges as to ensure a properly running program as most users will
>ultimately be running the same.  Provided things go well under those
>settings, being an Admin should be a breeze.
>
>So yeah, Vista is really picking about ActiveX, registry writing and file
>writing.  The Developer Best Practices and Guidelines for Applications in a
>Least Privileged Environment artivle is a real help and worth reading.  :-)
>
>- Kev
>
>"MikeD" <nob***@nowhere.edu> wrote in message
>news:OBBYFCTXHHA.1200@TK2MSFTNGP04.phx.gbl...
>|
>| "Kevin Provance" <ca***@tpasoft.com> wrote in message
>| news:udQXAtRXHHA.4872@TK2MSFTNGP03.phx.gbl...
>| > Well, apparently if you make VB6.exe and Link.exe at always run as
>| > administrator, this will solve some of the problem.
>| >
>| > What sucks is that I keep all my projects in their own folder, and Vista
>| > won't allow VB to write settings to the .vbp file.  Stupid Vista.  Too
>| > many
>| > workarounds.  :\
>|
>|
>| I don't know much about Vista yet, but from what I can gather from other
>| posts and just reading about Vista, try turning off UAC. From my
>understand,
>| with it own, most programs are going to "think" they're running under
>| non-admin accounts....even if you are logged on as an administrator.  To
>me,
>| this is no different than people trying to run VB (or any development
>| programs) under non-admin accounts in earlier versions of Windows.
>|
>| --
>| Mike
>| Microsoft MVP Visual Basic
>|
>

>It
>just kicked back a call to regsvr32 with the selected file as a command
>line.  I've not found a way to run a call to a program from the shell "as
>Admin".  I even peeked around as registry permissions...no go.  My hack
>won't wok on Vista, plain and simple.  Oh well...it just forces me to do it
>the way I should be doing it.  ;-)
>
>- Kev
>