|
Excel2003/Excel97 Object Library Conflicts
Hi all,
So we have a couple of legacy database systems developed using Access97 Applications, which then produce reports in Excel97 using old Excel97 Object Library references. When the Access97 dbase Apps are opened for use, they automatically search the local system for the version of excel installed and then proceeds to update the access97 system with the version of excel found. Now this all works fine, unless you have Excel 2003 on that machine, in which case it then picks up the Excell 2003 version and starts to use the Object Library for excel 2003, which then screws up the system as the Access97 dbase apps and are not written for 2003 version Object Libraries. so my question really is, how would you go about using the SVS solution to deal with this kind of situation?
Do you think virtualizing Excel 2003, might isolate Excel
Object Libraries and thus resolve issue. Any ideas?
I am also thinking, maybe virtualizing excel 2003, and if need be getting the user to "deactivate" the Excel 2003 while using the legacy SVS appz.
Any ideas appreciated.
Many thanks in advance.
|