Distributing Changes in Workbook

J

JohnGoogle

Hi,

This is a newbie question.

Suppose a worksheet has been developed and it was distributed to a
number of people who have been entering data into their own copies of
the workbook.

If a change is made in the 'master' worksbook to VBA code or a cell
formula to fix a problem, what is the best way to distribute the VBA /
formula changes to the different users while allowing them to keep the
data in their copies of the workbook?

I hope this question makes sense.

TIA!
 
D

Dave Peterson

This sounds like a good reason to distribute the VBA code as a separate workbook
(as an Addin). Then you could just tell the users to trash the old and use the
new addin.

But this may be too late for you.

You may want to try using some code at Chip Pearson's site:
http://www.cpearson.com/excel/vbe.htm

He has samples on how to write code to change code. In fact, maybe you could
write code to remove all the code. Then you could distribute the new procedures
as an addin.

As for changing formulas, you could have a procedure that changes the formulas
in cells. The bad news is you'll be at the mercy of the users. If they changed
the layout of the workbook--renamed sheets, inserted columns/rows, the locations
of the formulas you want to change may not be where you think they are.

======
And I have no idea if this will work....

Maybe you could distribute a new workbook, then extract the data from the old
versions so you could copy it to the new workbook.
 
A

aaron.kempf

dude throw excel out the window and use a DATABASE.

you can have multiple people entering numbers into a database at the
same time
i mean.. DUH
 
J

JohnGoogle

Thanks Dave for your reply. It confirms the limitations of excel that I
thought were there.

As for aaron, don't be such an arsehole.
 
A

aaron.kempf

im not an asshole...

i just constantly deliver spreadsheet replacement applications-- using
Microsoft ACCESS and I'm sick and tired of you spreadsheet dorks that
multiply like rabbits

more of you numbnuts need to grow into databases
 
J

JohnGoogle

Aaron,

If you're so a hot developer, why are you using a mickey mouse DBMS
such as ACCESS?
 
Top