Code on form in Navigation form does not work in ACCESS 2010

I am trying to learn how to use the Navigation form feature in ACCESS 2010.  I can create say, a new employee data form that checks the emp id for duplicates and that certain fields are required.  It then clears all the data after it is saved so the user can enter another employee.  However, when I moved this to the naviagation form, nothing works.  So, how to you get, or can you even get, validation code to run when the form is moved to the Navigation form feature in ACCESS 2010?  I really like it and do not want to have to go back to creating a different user interface for navigation simply because I cannot get validation code to work.
Sandra SmithRetiredAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robert ShermanOwnerCommented:
As far as I know, the code should work the same.   I would suggest looking at what form events are handling your validation code in the standalone form, and then opening the navigation form in design view and selecting the same form to confirm that the code is still present on the form from within the navigation form.  

The only reason I can think of off the top of my head for form code to NOT run under a navigation form, would be if the navigation form itself had some event procedure code that was interfering with / or not passing the events down to, the child forms on the nav form.

If you can post a stripped-down basic sample of a navigation form where form events are not firing, that might help us to track down the issue.   (no need to include any actual data, so long as you can confirm the form code isn't getting executed)
PatHartmanCommented:
Any form you put on a navigation form becomes a subform.  That means that any form field references must be changed to Forms!mynavigationform!myoriginalform.Form!controlname.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sandra SmithRetiredAuthor Commented:
Yes, that worked as well as changing reference from Me.name to simply Me.  Thank you, this was an issue as I did not want to have to re-write everything.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.