Hi
I wondered how people generally build their documentation up.
I have been keeping my own tabs on a database application I am building by tracking all the forms in the Db (since forms control the entire usage of the Db) in a Word document where I list the source table/query; what the form is for, in broad terms; any field events; any form events; and the VBA code on each command button on the form.
It is a cumbersome file but it helps me see programme flow and also track down very quickly where any query is used using <Edit> <Find> in Word.
I feel sure that there may well be better ways of doing this but I don't know how best to do so.
To give an idea of complexity the Db is split and the F/E is about 8Mb. The Word document is about 130 pages long now!
Any suggestions on best practice?
Thanks for any help
Best wishes
Malcy
I wondered how people generally build their documentation up.
I have been keeping my own tabs on a database application I am building by tracking all the forms in the Db (since forms control the entire usage of the Db) in a Word document where I list the source table/query; what the form is for, in broad terms; any field events; any form events; and the VBA code on each command button on the form.
It is a cumbersome file but it helps me see programme flow and also track down very quickly where any query is used using <Edit> <Find> in Word.
I feel sure that there may well be better ways of doing this but I don't know how best to do so.
To give an idea of complexity the Db is split and the F/E is about 8Mb. The Word document is about 130 pages long now!
Any suggestions on best practice?
Thanks for any help
Best wishes
Malcy