Using Microsoft Access Wizards
Using wizards in Microsoft Access shouldn't be a "hot issue" in any way. Somehow, however, it always seems to spark arguments among developers and power users alike.
On one hand, it's easy to click a few times, and have something automatically created for you that you can use. On the other hand, by using wizards to automatically create forms, subforms, reports, and queries, you are sacrificing a little bit of control you may have over the creation process in your database. Code is being automatically generated that you're not involved in, objects are being automatically created without your full control, and your database is changing the way Access was made to change it.
On one end of the spectrum, those who argue that using wizards is good because they don't want to learn any more than they have to are usually not going to get far past a learning curve that exists with Microsoft Access. On the other end of this debate, you've got individuals who will go out of their way to manually accomplish something that Access could do automatically simply because they are control freaks, or would rather not have Microsoft think for them.
In my opinion – both of those views are downright silly.
My own rule of thumb is this: If using a wizard can save you a little bit of time – and you know what changes it's going to make, then use it. If you'd rather maintain more control over your database, then don't.
Conspiracy theories aside, wizards are there to make redundant tasks automated and (arguably) a little easier.
I don't use wizards for query creation for two reasons. First, I know how to create any query that would normally be created by a wizard. Second, It doesn't save me any time. In my view, wasting time to go through an automated process goes against what the automated process is there for.
I will use wizards for some simple button creation on Forms. While I can create a combobox or listbox that allows me to navigate my own records, it's just easier for me to select an item or two in a wizard and have Access create the code and button for me. If I ever need to change the code, I know where to go and how to do it, so why would I waste my time from the get-go?
I'd suggest a similar approach on an individual basis. Don't refuse to use wizards for silly reasons. Make intelligent choices in how you operate Access to get done what you need to do. There's no more prestige in using them or not using them, the only thing you have to lose or gain is time.
©2010 Blue Moose Technology, LLC
Article Publishing and Re-Print Guidelines
- The article text, resource box, URLs copyright information and these guidelines must be left intact and unchanged.
- When re-published online, all links must be live hyperlinks.
- These articles may not be distributed in any manner that does not comply with federal communication guidelines. Be Good!
- These articles must not be password protected or limited to membership or paid-only viewing. Keep 'em free, folks!
You can easily link to this article!
If you'd like to link to this article from your own website, copy and paste the following HTML code onto your page:
On your page, the code will appear like this: