Re: and yet another Vista question
- From: "Galen Somerville" <galen@xxxxxxxxxxxxxxxx>
- Date: Sat, 30 Jun 2007 18:23:26 -0700
"MikeD" <nobody@xxxxxxxxxxx> wrote in message
news:eRTxHo3uHHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
Yes setup program run under admin account. ActiveX Installer Service is
"Galen Somerville" <galen@xxxxxxxxxxxxxxxx> wrote in message
news:u5ykzY3uHHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
"MikeD" <nobody@xxxxxxxxxxx> wrote in message
news:Ol5Yc02uHHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
My bad
"Galen Somerville" <galen@xxxxxxxxxxxxxxxx> wrote in message
news:%232aoaw1uHHA.3364@xxxxxxxxxxxxxxxxxxxxxxx
I have an app with numerous ocx's and dll's. I'm installing as Admin and
use a manifest file to avoid all the pop-ups.
Everything gets registered okay but one item fails.
My "strings" for different languages are in separate dll's. The dll's
are listed in the reference section of the IDE and all works well on XP
and 98. Here's a part of the code that fails:
On Error GoTo NoResource
Select Case gintLangBase
Case 0
Set clsRes = CreateObject("cds74eng.classcds")
strLogo = "\cds74eng.jpg"
GetResource = True
Case 1
Set clsRes = CreateObject("cds74esp.classcds")
strLogo = "\cds74esp.jpg"
GetResource = True
Case 2
Set clsRes = CreateObject("cds74frn.classcds")
gintLangBase = 0 and it Errors out on the first line of Case 0
I've tried installing cds74eng.dll on both System32 and the App folder.
In both cases I can look at the dll's properties and it is all
hunky-dory.
Any ideas?
What's the error? All you said was that it "errors out". That doesn't
tell us a thing.
--
Mike
Microsoft MVP Visual Basic
Run-time error 91
Object variable or with block variable not set.
Well....the only thing I can tell you from that is that the DLL is not
registered correctly. To my knowledge, that's the only thing that could
cause that error, *given your posted code*. There's actually lots of
different ways to get that error, but they all boil down to trying to use
an object variable that's Nothing. Since you're getting the error while
using CreateObject to instantiate the object, it pretty much means the
only cause could be that the DLL isn't registered properly (and a manifest
file to elevate permissions for your app isn't going to solve that).
Things are different in Vista due to UAC. I assume this DLL is installed
by a Setup program that was run under an Admin account? Is the app being
run by a different user? I believe that a service called something like
"ActiveX Installation" must be started (and remain running) in such a
scenario. A Vista newsgroup might be a more appropriate place to ask this.
Personally, I don't see this as a VB problem, but as a security issue with
Vista.
Hopefully, somebody who has more experience with Vista than I do will
help. For the time being, I'm lucky because I have no "publicly available"
apps out there for which I'd need to support Vista. I work for company who
is a MS partner and we support their MBS product line (Great Plains,
Solomon). We're telling our clients that at this time, upgrading to Vista
is not advisable unless they also update their Great Plains or Solomon
software to versions that have just been released (as of about a week
ago).
--
Mike
Microsoft MVP Visual Basic
turned on. Clicking properties on the dll under security, etc, shows it's
valid under SYSTEM, Admin and User accounts.
So far no customers have ordered Vista machines, but it's going to happen
darn it.
It appears they will require an Admin User account. If I can get past this
error then I can try it in a standard user account.
Galen
.
- Follow-Ups:
- Re: and yet another Vista question
- From: David Youngblood
- Re: and yet another Vista question
- From: David Youngblood
- Re: and yet another Vista question
- From: Steve Gerrard
- Re: and yet another Vista question
- References:
- and yet another Vista question
- From: Galen Somerville
- Re: and yet another Vista question
- From: MikeD
- Re: and yet another Vista question
- From: Galen Somerville
- Re: and yet another Vista question
- From: MikeD
- and yet another Vista question
- Prev by Date: Re: and operator
- Next by Date: Re: Code Editor Annoyance; mouse wheel
- Previous by thread: Re: and yet another Vista question
- Next by thread: Re: and yet another Vista question
- Index(es):
Relevant Pages
|