R
Rob Nicholson
The base standard for ADO on a Windows 2000 PC is ADO v2.5. Therefore, we
develop our Excel based application referencing this version. However, Excel
has a very annoying habit of automatically upgrading references to ADO in
the following situation:
o Developer saves with reference to v2.5
o User A with ADO v2.7 opens the workbook
o Excel upgrades the ADO reference to v2.7 (even though v2.5 is also on
there)
o User A saves the workbook
o User B with basic Windows 2000 PC (thus v2.5) tries to open workbook but
can't as it references a library they don't have
I realise we could use late binding but that really slows down development
as intellisense doesn't work and therefore typos occur.
So...
a) is it possible to disable this automatic upgrading (I suspect not)?
b) is it possible to access the referencing mechanism during start-up to
force binding back to v2.5?
Thanks, Rob.
develop our Excel based application referencing this version. However, Excel
has a very annoying habit of automatically upgrading references to ADO in
the following situation:
o Developer saves with reference to v2.5
o User A with ADO v2.7 opens the workbook
o Excel upgrades the ADO reference to v2.7 (even though v2.5 is also on
there)
o User A saves the workbook
o User B with basic Windows 2000 PC (thus v2.5) tries to open workbook but
can't as it references a library they don't have
I realise we could use late binding but that really slows down development
as intellisense doesn't work and therefore typos occur.
So...
a) is it possible to disable this automatic upgrading (I suspect not)?
b) is it possible to access the referencing mechanism during start-up to
force binding back to v2.5?
Thanks, Rob.