Quote:Why not have a command button that executes your code based on the setting in the other elements? Or if you still want full fuctionality, you can still use SetDefaultTab() instead of Startup Form.
Both are possible, but neither are clean.
With your first suggestion, you force the user to initiate actions that should be able to happen automatically. And also, it doesn't solve all issues. As per the example I presented, you'll still be stuck with having a check box be able to exist in a NULL state.
Your second suggestion is better. It overcomes most of the shortcomings I mentioned. However, it's aesthetically awkward. This is because you now have, on startup, two tabs. One called Application Menu, which effectively serves no purpose (especially when using -closed on startup) and one called (using the programming example in the documentation) "Search/Update Main Menu". "Search/Update Main Menu" is a confusing tab name for the user, as it isn't really a Search/Update window.
The cleanest solution would be to have a fully functional form exist as the Application Menu tab.