Navigation form in Access 2010 producing error first time a different tab is clicked

[Seth Schrock]

I have created a navigation form in Access 2010 using the horizontal tabs, 2 levels style. This form is my startup form. In the top row, I have to options. Under each option are several sub-tabs with forms bound to them. When I first open the database and click on the second of the two main tabs, I get a VBA error message saying This action will reset your project, proceed anyway?. If I click OK, I can then click back and forth between the two main tab without any problem I can even click on the sub-tabs. If I close the form and reopen it and try to click on the second main tab, I get the error message again. I have no code or macros in any events in the navigation buttons, controls, or the subform, so it must be an internal code that is running and causing the error. I have no idea how to troubleshoot this, but I've go to get it fixed before I can publish this database as I'm sure that Access Run-time will crash when this happens as it doesn't have any error handling capabilities.

How can I stop this error message?

Edit: I just tried making a new form and adding the navigation control with the same setup and it doesn't get the error. So I might just try starting over as there isn't much code to copy over. I would still like to know what caused this so that I can keep from having this issue again.

[zmbd]

Seth
Search this site use "ZMBD" "Navigation Control"
>removed bad link

You'll note that the ACC2010-Navigation Control has some quirks.

One of which is that if you use a two (or more) tiered control panel and the parent "Has Module" is true, you're sunk - period. So the "ON Load/Open/etc..." events cause an issue. SO will any code in command buttons etc...

You need to move the VBA from Subs to Functions for all VBA used in the ACC-2010-NavigationControl parent form and then use the MACRO language to call the VBA functions. THUS< the parent form "Has Module" property stays false/no and you can still use the VBA script.

Welcome to the NEW and IMPROVED switch board concept.

[Seth Schrock]

So if I reduce my number of levels to one, are there any limitations on the code?

Your link doesn't work. I did a search through Google, and I got 1270 results. Anything else to narrow it down? I looked at the first two results and didn't find anything that I hadn't already discovered in my own research.

[zmbd]

Should work; however, if you create the accde version, be prepared to also move to macro level triggers for the parent form.

(sorry about the bad link, thought the bytes.com would stay put - nonetheless you did find something :) )

[Seth Schrock]

I'll give that a try tomorrow when I get to work. I don't use the accde version as the users are only running Access Runtime and don't have any database editing capabilities anyway.

It sounds like I will need to learn how to use Macros to call VBA functions if I want to keep using the navigation control in the future though.

[Seth Schrock]

It works now. I moved all the code to another module and used macros to call the functions and I no longer get the error message when changing the first level tabs.

Thanks Z.