Anyone have any experience using the above methodology within an Access VBA Application?

Would really appreciate some pointers in working in this way within a VBA-based project.

Any/All input gratefully received.

Kind Regards
Rob

<center>"Nothing can stop the man with the right mental attitude from achieving his goal;
nothing on earth can help the man with the wrong mental attitude".
Thomas Jefferson</center>

__________________
Rob
http://cantgrokwontgrok.blogspot.com

I think you can use this methodolgy with VBA, but the thing is that most of the code is already written in Access (forms, reports, tables, data structures, queries etc). Most VBA coding involves just putting subroutines and functions in on specific events, so there is not much in the way of coding oversight needed to this degree.

Of course it is always good to ask the typical questions like How will I know when the problem is solved, before coding. But since most of it is already done, VBA is kind of like content management more than a true coding environment. So I just don't feel that, other than requirements and UAT that this much rigorousness is needed, IMHO.

HTH

mmcdonal