How to provide updates to VISIO+EXCEL project code, without always issuing new versions of the full project files?
Posted on 2013-06-06
Part of my visio+excel project contains 'tools' that users can employ to gain additional effects. These tools are vba procedures, and additional tools will be added over time.
I wonder how/whether to update the project files actually held by users, between times that a new version of the project is issued.
As a vba user, I'd like to assemble the project code in a way that is most accessible to whatever automated updating can be applied later in the project (when more skills may be available).
1. Tell me if any elements of this are really a practical issue this early stage?
-- If so, can you give some pointer urls for visio and excel?
2. Help me with this memory (if its accurate). I think I've read David Parker as saying (roughly) ~ that a well-used method for adding code to Visio is by means of .vss files / masters ~ . I noted the url and lost it! (And I cant imagine how it would work.)
-- If this memory is actually true, this suggests that scope for updating /adding code
in visio can be somewhat different from the methods for excel?