I would think that he could install the new macros without destroying the
database.
Well, I would hope he could. Of course if the code change required a
database structure change, that could be a problem. Also, printing commands
could be affected by transferring to a different mainframe, and there is the
software compatibility to worry about, versions, etc. A lot of detail. No
matter how you do it there will still be loose ends, so just pick one and go
with it. Work out the bugs as you go.

"Ed" wrote:


"JLGWhiz" wrote in message
...
Why not use CDs, that is pretty cheap and will not overload the mail
server
if you send them USPS.


Thanks for the reply.

The problem is the data. the VBA code seems to be unavoidably part and
parcel with the
data, i.e., all the worksheets in the workbook. So, lets say I send
the new guy a CD with
the current membership state, e.g., list of members, addresses, dues
payment status etc.,
and of course the current set of VBA macros. He works with it for a
month or two and in
that time updates some of the addresses, some members pay their dues,
etc. He then calls
and says, "Hey, Ed. Why don't you fix ....." That is, he doesn't like
the way some of
my macros work. If I fix the macros and send him a new CD he has new
macros but
old data. If he copies my new xls file into the membership directory
on his machine he wipes
out his last two months of work.

How do I get around this?

thanks again.

Ed