Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access VBA
Password Reminder
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Access VBA Discuss using VBA for Access programming.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access VBA section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old July 23rd, 2007, 10:33 AM
Friend of Wrox
Join Date: Mar 2007
Location: Hampshire, United Kingdom.
Posts: 432
Thanks: 0
Thanked 1 Time in 1 Post
Default Test-Driven Development (TDD) within Access VBA

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

<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>
Reply With Quote
  #2 (permalink)  
Old July 24th, 2007, 07:24 AM
Friend of Wrox
Points: 9,611, Level: 42
Points: 9,611, Level: 42 Points: 9,611, Level: 42 Points: 9,611, Level: 42
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Mar 2004
Location: Washington, DC, USA.
Posts: 3,069
Thanks: 0
Thanked 10 Times in 10 Posts

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.


Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Development Environment for Access 2003 Loralee Access 2 January 21st, 2006 03:22 AM
Microsoft Access Application Development Richard Hunter BOOK: Expert One-on-One Access Application Development 1 July 15th, 2005 02:50 PM
licensed for development and test only mp VB.NET 2002/2003 Basics 1 April 10th, 2005 04:55 PM

All times are GMT -4. The time now is 12:05 PM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.