Build VBA instead of MACRO

C

Chuck

A recent upgrade from Access 2003 to 2007 has left us with some questions
that we could usually find an answer for in the groups. However, this one
has us stumped. In Access 2003, when adding a command button to a form and
using the wizard, it would build the VBA code. The button properties could
then be edited in the OnClick event. Now, in Access 2007, the wizard builds
a macro and if any code needs to be written, the conversion from macro to
VBA has to be performed, each and every time a command button is added. Is
this the way Access 2007 is supposed to work now or is there an option that
we missed to build code and not use macros?
 
A

Allen Browne

If you use the new file format (ACCDB), the wizard will generate an Embedded
Macro.

But if you use an MDB in Access 2007, the wizard will create VBA code.

So, unless you need something in the new file format (such as multi-valued
fields), you might be able to solve the issue by using an MDB.

(The reality is that the Wizard doesn't make very good VBA anyway.)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Using expression builder object 2
Example Of VBA SQL Statement 0
Create Outlook Contact 1
How do I run vba code in Access without a macro window opening? 3
Access 2007 runs VBA code faster 1
Macro that will insert a simple text string in top cell of text file 1
VBA Reference Libraries-Access 2003 vs 2007 6
vba macro that allows insertion of symbols at cursor 0

Top