Access 2010 now creates macros instead of VBA code

[mafhobb]

I have been using 2003 for a while but I have switched to 2010 recently.

I have just found out that if you use the wizards when creating a command button, Access now creates a macro instead of creating VBA code (for opening a form, for example)

I prefer code over macros, so is there a way to change this?

Also, what about the macros that have already been created?? How can those be converted to VBA?..When I use the "Convert From's Macors to Visual Basic" option I get a "There was a problem opening the macro "[Embeded Macro]". Do you want to continue?" and the macro does not get converted.

mafhobb

 

[Galaxiom]

Even with 2007 where the Wizard makes VBA I usually make one button, abandon the Wizard at the first opportunity, then delete everything except the first and last line. Then I adjust the button to my aesthetic whim and copy using the clipboard for all the others on the form (and often the other forms in the same database).

I write all the code. If I need Error handling in a procedure then I add that at the end of the project with the facility in MZ-Tools.

 

[mafhobb]

This is dissapointing...

After some research it looks like this is a know Access 2010 bug. I guess MS is working on it. I wonder when we will have a fix. In the meantime I'll ignore the wizards and write the code myself.

mafhobb