does anyone know of any tools, free or commercial, for managing vba code in excel workbooks?mainly its to get around the problem of having a lot of spreadsheets all with their own copies of commonly used code. i would like to keep vba code in modules separate from the spreadsheet itself, and then at "build" time import al the various modules into the sheet & compile the vb.

You can do exactly that by using the personal workbook feature of Excel - or package all comon code in an add-in.

yes, but it's on a bit of a bigger scale than that. we have many spreadsheet based trading apps & many add-ins, some built in vba and some in c++.with c++ code, you can keep it all in source control with versioning, history, etc etc & compile it into the dll/xll when you need to do a new release.with pure vb code, if you keep it in a spreadsheet (by which i mean either .xls or .xla) then (1) you lose all the benefits of the source control as you can't view, compare, version & manage the code directly, only the complete spreadsheet(2) if somehow the xla becomes corrupted, then you've lost all your vb code. This can happen frequently if you have sheets which reference many dlls etc, as excel often gets confused.neither of these would happen if you stored all the code separately as .bas, and compiled it all into the spreadsheet again for each new release of the application. hence the question.it's easy enough write something to import a bunch of code & "build" your spreadsheet, but i though maybe there is already a solution out there.

Subversion can verson control any type of file - not just source code......it can even vc binaries.

The Subversion website is here and a really nice windows explorer client is TortoiseSVN

Sounds like you need an excel addin capable of extracting code modules from another xls or xla so that both the sourceless binary and the source modules can be entered into a source control system for not just versioning but diffing. On the way out of the source system it would then do the opposite.Im not aware of anythign preexisting but I dont think it would take much code if you look up how to use the object model of the visual basic editor.

afoster....thx for your reply, unfortunately we already have a source control system, & changing it to a different one is not within my powers.patch22...yes, that's the idea. i could indeed reasonably easily bosh something together myself, but i am hopeful that someone's already done a proper job of it & made it available.

hi all,can any one provide me with an e-book on VBA for Excel.my mail id is saini@eruditee.comRegards saini