I want the control wizard to create VBA code, not embedded macros. I checked
the "Always use event procedures" box in the Access Options - Object
Designers, but the wizard still creates embedded macros instead of VBA code.
What I am missing?
I want the control wizard to create VBA code, not embedded macros. I checked
the "Always use event procedures" box in the Access Options - Object
Designers, but the wizard still creates embedded macros instead of VBA code.
What I am missing?
An event is something a user does, the procedure is what the program does based on the event. A macro is a procedure.
That's my understanding anyway.
Macros are easier for users to edit that dont know VB. They both work.
If you want to use VB, click the elipsis button at the event property, then click CODE BUILDER
That checkbox affects the codebuilder to automatically choose VBA. The wizard builds macros.
Here's a site that shows how to convert a macro to VBA
http://rogersaccessblog.blogspot.com...-vba-code.html
That's exactly what I thought, but, it doesn't take effect.
I really need that feature for smooth work.
By the way, the conversion doesn't work. I've tried several times always got the same error:
"There was a problem opening the [Embedded Macro]. Do you want to continue?"
Perhaps you could post a copy of your database so readers could see the issue based on their "access" parameters.
You have to completely delete any embedded macros from controls. One way may be to erase all of the text [Embedded Macro] within all events before adding any VBA. Another approach would be to delete the control and rebuild it. So it is likely you will need to copy and save any VBA generated by Access. Long story short, controls can be fickle and become corrupt.