My (UK based) company built a simple accounts system in Excel about 10 years ago. This was for internal use only and it is still active. We now want to develop it (Excel 2003) so that it can can handle overseas transactions. This certainly looks very tricky.
As background analysis to this development, we have described (in general terms) both the VBA Forms and the General VBA code used to run the system. However, I am finding it very much more difficult to describe the structure and purpose of the worksheets themsleves, without overloading it with too much detail about individual cell relationships.
Do you have any suggestions about how to describe a spreadsheet based system (not a database) that does not overload it with detail? The latter caveat is intended to avoid re-building the systems itself.
Stephen Allen
ACBA (UK) LTD
As background analysis to this development, we have described (in general terms) both the VBA Forms and the General VBA code used to run the system. However, I am finding it very much more difficult to describe the structure and purpose of the worksheets themsleves, without overloading it with too much detail about individual cell relationships.
Do you have any suggestions about how to describe a spreadsheet based system (not a database) that does not overload it with detail? The latter caveat is intended to avoid re-building the systems itself.
Stephen Allen
ACBA (UK) LTD
