Determine if VBA is installed

[vnanney]

Is it possible to determine programatically if VBA is installed - does VBA have certain registry keys or other that is associated with a valid VBA installation??? We have run into several situations where users would have Excel installed, but did not install any VBA support with it. Thus would like to determine if our install can detect this situation to prompt the user as to the issue.

TIA

 

[SkipVought]

Hi,

Hmmmmmmm? Use VBA in order to discover if VBA is installed?

You may want to post this kind of question in forum222 maybe?

Skip,
^{Don't let the Diatribe...
talk you to death!}
_{Just traded in my old subtlety...
for a NUANCE!}

 

[vnanney]

Our applications are not VBA, but C++/C# based and support a VBA framework via VSTO and XLL based UDFs. But without VBA support the framework does not function and was hoping a VBA programmer might be able to provide some insight into the VBA environment since MS isn't being too helpful. Thank you for your response - I will look into the other forums as you suggested.

Have a nice day!

 

[strongm]

>Excel installed, but did not install any VBA support with it

???

I have no idea how you'd achieve this. VBA can be disabled in each of the Office products (and, generally, in 3rd party apps that incude VBA) through security settings, but I wasn't aware that Excel could be installed without VBA.

I'm wondering whether perhaps the problem you are encountering is not the one that you think you have ...

 

[PHV]

I wasn't aware that Excel could be installed without VBA
Perhaps the XL viewer ?

 

[MakeItSo]

Excel installed, but did not install any VBA support with it.

I suppose they did not install the VBA help with it.
If it is Microsoft Excel as part of the Office suite, then VBA is always part of it.

[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[fumei]

If it is just a Viewer, then it is not an actual install of Excel. If Excel itself is installed, then VBA is there, at least with the install. I do not think Excel could even run if VBA was not there. It uses VBA procedures internally to function.

If there is an issue - not really defined - could it be that whatever code your C++/C# code is executing is not fully qualifying VBA?

Gerry

 

[AnotherHiggins]

I suppose they did not install the VBA help with it.

Given the quality of VBA's help files, that might not be a bad thing.

[tt][blue]-John[/blue][/tt]
[tab][red]The plural of anecdote is not data[/red]

Help us help you. Please read FAQ 181-2886 before posting.

 

[vnanney]

I am sure the problem is VBA not being installed with the office suite. Office/Excel 2000 and older will always have VBA installed, but Office 2003 & 2007 installation of VBA is optional( look at the 2003 & 2007 install screenshots attached if you don't believe me) I guess MS decided to go this route so IT security will still let people have the office suite, but no VBA security risks. ( yes, it's sorta like giving someone a wheelchair with only 1 wheel). And this is the situation we have encournted. Users have office suite but no VBA installed. Thus back to my original question - is anyone aware of registry keys, files or other that are associated with VBA hat might be used to determine if VBA is installed????
Thanks for the feedback!

 

[PHV]

Look at %CommonProgramFiles%\Microsoft Shared\VBA\VBA6\VBE6.DLL

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[strongm]

Might I suggest the following API call: MsiQueryFeatureState
And you are looking for "VBAFiles"