Actually, like Paul, most of the experienced developers, here, don't use Macros. But some testing shows that placing
[NewRecord]=True
under the 'Condition' in your Macro, to the left of the 'Action,' does the job.
But you really should take the time to learn VBA. It's much more flexible, and you only have to go to the code module to see everything that is going on in your Form, rather than having to open each Macro, in turn. This makes figuring out what is going on in your Form, or more importantly, what is going wrong in your Form, much less labor intensive.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007