![]() Have you found an approach that totally makes the issue go away? Have you been able to use it for justification to migrate a spreadsheet to another technology? How do you manage this proliferation? Do you have tools? do you rely on good (de-coupled) design? Do you just re-issue a new master? and if so how do users move their existing analysis to the new version? It does pretty much everything, although I have found some of the VBA replacement stuff to be mildly unstable at times. I have a VBA based ‘patch’ tool that I use for scripting version management stuff so I can keep these distributed apps in line. Excel Services could also help, (if people are connected I think?). But equally splitting data and logic into any separate components could help. This is one area where VSTO/.net could add some real value. ![]() If its just a couple of users, well then that seems easy enough, but actually if they are sitting on 50 copies that all need updating and assuring as consistent, then thats a bigger job. The thing I am thinking about is the maintenance headache when you realise you need to make a change to a live spreadsheet. Maybe 1-5 are live at any time, but they probably create 20/30/40 or maybe more per year. But at least double that use it, and they each probably have literally hundreds of copies. One example I mentioned in the distribution post was meant to be for 30 (named and trained) users. Much of my stuff is for 1 or 2 users, but they may end up with 10, 20 or 30 versions per reporting cycle. How many copies of your spreadsheet application end up ‘live’ on the network? In itself thats quite interesting, but I think I missed a question. On the distribution front many of us seem to be targeting a handful of users for most Excel/VBA applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |