"New2VB" wrote in message
...
I am using Ron Debruin's menu system, which is working perfectly, to drive
an
application I have developed and have a couple of questions from a
housekeeping perspective:

The forms and associated code I developed in my application to run the
various menu options must now reside in the add-in, is that correct?

Yes

The modules I developed in my application to run other components (not
form


Yes

related) must now reside in the add-in, is that correct?
The sheets that hold the data must sit in the original worksheet, is that
correct?


Yes

If my assumptions are correct, then it means every time I do a system
update, I need to redistribute the add-in to all users and get them to
copy
it to their local drive where their Addins are stored. If I could maintain
all the modules, forms, sheets and associated code in my original
spreadsheet, which is the one users access to run the system, it would be
much simpler to manage the updates as I store that file on a central
server.

If all I had to do was manage Ron's QAT menu system, which will change
very
infrequently, via the addin, updating the system would be a breeze.

Does anyone have any suggestions that might make things a bit simpler to
manage the updates?

The simplest way is to hold a master copy of the addin in a server location
that everyone can access. The addin would store the version number
somewhere, say in a worksheet cell. You would then have another (control)
file that could simply be a text file, and when your client addin starts it
reads that control file and checks the version number. If they are not the
same, advise the user to download the new version and install it - you can
give detailed instructions.