[AccessD] Access refuses to embed event procedure for new command buttons

I found some help on this on the web, Thank God! The command to convert is
not object-specific, it is for all the form's macros in one shot - in the
Controls group of the Design tab on the ribbon. so I just have to let the
controls get created with embedded macros, then convert. The option that
seems like it would do this is for a different purpose, and for creation of
objects within MDBs, not ACCDBs, according to what I have read somewhere.

 

From: Bill Benson [mailto:bensonforums at gmail.com] 
Sent: Sunday, January 11, 2015 1:54 PM
To: 'Access Developers discussion and problem solving'
Subject: Access refuses to embed event procedure for new command buttons

 

Ac2013.

 

I have set the option to always use event procedures in forms and report
designers in the Acces s options, restarted access and the database - but
Access refuses to offer this, it keeps embedding macros when I add controls
with the controls wizard. Also, because they are embedded, I cannot see how
to convert them to VBA procedures, as I used to when I could find them in
the object navigator.

 

Is there corruption here or is there something I can do about this, it is
really frustrating to me. It used to put in the click event, now it has
switched to and embedded macro, without my doing anything I am aware I have
done.

 

TIA.