Various Version References = Compile Error

[DS]

Hi all,

I have a workbook with some additional references, specifically:
Microsoft ActiveX Data Objects (Multi-dimensional) 2.8 Library
Microsoft ADO Ext. 2.8 for DDL and Security

And this works just fine on my computer.

However, when some other users utilise the functions that require these
references, they get a compile error, due to missing references. When I go
into it on their pc, I find that they have the above references only to 2.5
or 2.7 available, so have to manually alter the references on the copy
they're using to the earlier version, at which point it works fine for them.
Until they re-open it and try to use it again....

Is there any way around this short of trying to badger IT into giving us all
the same versions of Excel (which, to be honest, would be more work than
going to their desk every time they use it and manually updating them....).
If I set these references to the earliest version 2.5, would users who have
2.7 or 2.8 be able to use it ok, or would they be gettinng compile errors as
they don't have 2.5 specifically?

Many Thanks folks
DS

 

[JLGWhiz]

If I were the executive in charge, I would update to the latest version for
all workstations. The cost savings of lost manhours would more than pay for
it.

 

[NickHK]

Assuming the older versions contain all the required functionality, create
you WB on a machine with the oldest expected versions.
When used on a machine with newer versions, they will be updated. (Newer
versions are not "downdated" to older versions though, hence your problem.)

Or look into using late binding and hence no reference problem. This may be
an option if you do not have any "With Events" on these classes.

NickHK

 

[DS]

Hi JLGWhiz,

I agree. Unfortunately, I'm not in charge, and the person who is doesn't
really get the concept. I'm currently fighting with him in order to get a
2003 patch applied (at zero-cost for the patch) as anyone currently using
Office 2000 can't get past the "MS Excel has encountered a problem and needs
to close..." error on opening a number of workbooks, and therefore has to use
someone else's Office 2003 machine. This fight has so far lasted 5 weeks and
has no end in sight....

So, although that would be ideal, it's simply not practical!! =

 

[DS]

Hi Nick,

thanks for your response - this is what I did last night (UK time, before I
left for the day), using one of my colleagues' machines. I wasn't sure if it
would work ok, hence the post, and waiting for everyone else to leave for the
day before trying it!

Fingers crossed, it all seems to be working all right at the moment.

(Reason for the problem was that I wasn't aware of the varying versions of
these references when building - like a fool, I thought that maybe they'd be
the same! Boy, I shoulda known better).

Cheers
DS