Folks €“ What is the best practice for managing changes to the metadata
supporting workbooks? I have a workbook that contains a few frames, named
ranges, etc. The workbook will be distributed to roughly 50 to 100 users.
Unfortunately, we are not able to use Access or some form of shared network
drive. Each user will have their own instance of this workbook stored locally
on their workstation. What would the best practice be for managing updates
to the workbook after distribution to the end user?

For example, Im thinking of placing all of my lists/named ranges in one
worksheet called €œlists€�. The logic being that as lists are updated, I can
somehow send the worksheet to each end-user asking them to copy/paste or
otherwise overwrite the data on the €œlists€� worksheet within their workbooks.
Is there a better way to seamlessly update this information? Furthermore, is
there a solid practice for updating the code within modules and frames? I
suppose Im looking for the most efficient method of updating the things that
make the workbook sing and dance with the least amount of manual input from
the end user.
Any advice is much appreciated,

- mike

Well, we'll test your bold statement that any advice will be
appreciated! :Bgr

It's not clear what your users will be doing with the workbooks -
whether they will be addiing data on some worksheets, or adding formulas
on worksheets or adding new worksheets.

From what you did say, I'd almost suggest flipping your contemplated
approach around. Instead of sending them a worksheet they will have to
modify and incorporate into their existing version of the workbook,
would it be possible to restrict their customizations to a few
worksheets and have them copy those custom worksheets into the next
version workbook?

Again, not being sure what the users are doing with the workbooks this
may be a totally impossible suggestion, but at least you didn't pay a
lot for it! I'd appreciate hearing what you finally decide to do on
this.

James

PS - doing it this way would avoid the issue of having the end-user
over-writing / replacing code modules...


--
jamescox
------------------------------------------------------------------------
jamescox's Profile: http://www.thecodecage.com/forumz/member.php?userid=449
View this thread: http://www.thecodecage.com/forumz/sh...d.php?t=112076

James - that is good advice. My users will be adding data within the
workbook, either via a form or directly within a worksheet. Maybe I can work
some type of import process into the workbook thereby giving the user the
ability to import their data into updated versions. This gives me something
to think about.

thanks, mike

"jamescox" wrote:


Well, we'll test your bold statement that any advice will be
appreciated! :Bgr

It's not clear what your users will be doing with the workbooks -
whether they will be addiing data on some worksheets, or adding formulas
on worksheets or adding new worksheets.

From what you did say, I'd almost suggest flipping your contemplated
approach around. Instead of sending them a worksheet they will have to
modify and incorporate into their existing version of the workbook,
would it be possible to restrict their customizations to a few
worksheets and have them copy those custom worksheets into the next
version workbook?

Again, not being sure what the users are doing with the workbooks this
may be a totally impossible suggestion, but at least you didn't pay a
lot for it! I'd appreciate hearing what you finally decide to do on
this.

James

PS - doing it this way would avoid the issue of having the end-user
over-writing / replacing code modules...


--
jamescox
------------------------------------------------------------------------
jamescox's Profile: http://www.thecodecage.com/forumz/member.php?userid=449
View this thread: http://www.thecodecage.com/forumz/sh...d.php?t=112076