See for example “ Declaring API functions in 64 bit Office” ( ) which can involve extensive editing of your libraries and applications. If you are a VBA programmer you run risks such as having to upgrade your procedure libraries (“UW.dot”) to accommodate new features in the language. Then you run the risk of alienating clients who are still using Office 2018/2017/2016/… or whatever.
If you provide paid training to your own clients, you are susceptible to temporal risk while you take fresh screen snapshots of every dialogue box in your training material and rebuild (and reprint, bind etc) each training manual.
If you run a four-room twelve machines per room training centre, you are susceptible to a financial risk with each new version of Windows and/or Office, for your clients will insist that their people will be trained on Excel365″ or “Word2019”, even though the Introduction To Excel course uses only features found in Excel4.0.
So I would ask you “What do you mean by risks (to you)?” “It seems weird seeing people say that you might be willing to take the risks without saying what they are.”
0 kommentar(er)
