ANY way to trap a missing ref error without allowing access to VBA Project?

[Myriad_Rocker]

I have a VBA application in Excel that is used in multiple versions of Excel (2003, 2007, 2010). It is also used on x86 and x64 servers. The crux of the problem is that when a user downloads my application and puts it on an x64 system, there is a reference that points to just the "Program Files" directory instead of "Program Files (x86)". This causes the reference to be missing.

I cannot let this application access the VBA Project due to security reasons.

Is there any way I can trap this error (Compiler Error in Hidden Module or something like that) and just pop up a message box that tells the user that they have to change that reference?

 

[sous2817]

Couldn't you check if the OS is 32 or 64 bit at runtime and set your reference in the code?

Have a look here and see if you can adapt it:

http://www.eggheadcafe.com/software/aspnet/33677042/api-to-determine-if-os-is-32bit-or-64-bit.aspx

 

[Myriad_Rocker]

Couldn't you check if the OS is 32 or 64 bit at runtime and set your reference in the code?

Have a look here and see if you can adapt it:

http://www.eggheadcafe.com/software/aspnet/33677042/api-to-determine-if-os-is-32bit-or-64-bit.aspx

Wouldn't setting the reference in code require access to the VBA project?

 

[sous2817]

Maybe I'm confused...Did you write the VBA application, or is this something that you're trying to adapt.

I gathered from your initial post that you wrote the VBA application. If that's the case, then have your application check the OS type and set the reference then. I don't see why the end-user would have to get involved.

Of course, I could be completely missing something...

 

[Myriad_Rocker]

Maybe I'm confused...Did you write the VBA application, or is this something that you're trying to adapt.

I gathered from your initial post that you wrote the VBA application. If that's the case, then have your application check the OS type and set the reference then. I don't see why the end-user would have to get involved.

Of course, I could be completely missing something...

Yes, I did write the application. The reason that the user would have to get involved is because they are the ones that are using it. And depending on the server (64 bit or 32 bit), the reference has to be changed. I'm not involved at that point.

From my understanding, you have to "allow access" to the VBA Project, which opens security holes. It's an actual setting. I can't do that for security reasons at customers.

Does that make sense?

 

[RoryA]

Unfortunately no -you can't test to see if the references are broken unless you have trusted access to the VBProject.