[FONT="]I'm currently using Excel 2016 and i'm the original creator of the file / code. However, the goal is that everybody from my department (25 ppl) work in my file.
[/FONT]
[FONT="]Some of them are still on Win7 & excel 2013. This is a problem since every time I (or someone else with win10 & excel 2016) save the file, the references get updated to Microsoft PowerPoint Object Library 16.0. Excel 2013 doesn't have 16.0, only 15.0. Each time a 2013-user tries to run it, he gets an error since he is looking for "MISSING: Microsoft PowerPoint 16.0 object library". He needs to untick 16.0, activate 15.0, save the workbook and then execute the macro.[/FONT]
[FONT="]
[/FONT]
[FONT="]My question:
Is it possible to write some code in the workbook that checks what excel you are running and deactivate/activates the correct reference?[/FONT]
[FONT="]It would imply that I can save the worksheet in my excel 2016 and that a user with 2013 can click it, get its references updated, execute the macro.
Please note that users don't have admin rights. I know that my code is currently protected with a password, so i'd probably also have to remove that.[/FONT]
[/FONT]
[FONT="]Some of them are still on Win7 & excel 2013. This is a problem since every time I (or someone else with win10 & excel 2016) save the file, the references get updated to Microsoft PowerPoint Object Library 16.0. Excel 2013 doesn't have 16.0, only 15.0. Each time a 2013-user tries to run it, he gets an error since he is looking for "MISSING: Microsoft PowerPoint 16.0 object library". He needs to untick 16.0, activate 15.0, save the workbook and then execute the macro.[/FONT]
[FONT="]
[/FONT]
[FONT="]My question:
Is it possible to write some code in the workbook that checks what excel you are running and deactivate/activates the correct reference?[/FONT]
[FONT="]It would imply that I can save the worksheet in my excel 2016 and that a user with 2013 can click it, get its references updated, execute the macro.
Please note that users don't have admin rights. I know that my code is currently protected with a password, so i'd probably also have to remove that.[/FONT]