I’m trying to create a “wizard” like way to go through a series of steps to setup a job (requiring changes to multiple tables through many different views created by queries) by clicking a “Next” button. A back button would also be available if that makes a difference. I see a couple of options, but would like some advice as what considerations should be made to choose the best option. New ideas are welcome too! This is the first time that I have done something like this, so I have no personal experience with any of these ideas, so don’t laugh too hard.
1. Create a separate form for each stage of the wizard and have the Next button open the next form and close the current form. I don’t really like this idea because of the delay between clicking next and being able to actually edit the next form. Forms can sometimes take a while to load if the computer is running slow.
2. Use tab controls with each stage of the wizard on a separate tab. The Next button just sets the focus to the next tab. This could lead to a lot of controls to load at the beginning making it take forever.
3. Use code to change the recordsource of the form to the next query. The queries could be setup so that the fields are aliased to generic names such as “Field1”, Field2”, etc. so that control data sources wouldn’t have to be changed. Controls that aren’t used could be made invisible. This would require a lot of code.
4. Have each stage as a subform and just edit the visibility status of each form as needed. Might have to resize and change the location of each subform as they are made visible.
Like I said, this is new to me and these are just the ideas that came to me. Criticism of any or all of my ideas is welcome. I believe that I can implement each of these solutions, so exact details aren’t needed, just which path I should take. If I stumble on the chosen path, I will post that separately.
1. Create a separate form for each stage of the wizard and have the Next button open the next form and close the current form. I don’t really like this idea because of the delay between clicking next and being able to actually edit the next form. Forms can sometimes take a while to load if the computer is running slow.
2. Use tab controls with each stage of the wizard on a separate tab. The Next button just sets the focus to the next tab. This could lead to a lot of controls to load at the beginning making it take forever.
3. Use code to change the recordsource of the form to the next query. The queries could be setup so that the fields are aliased to generic names such as “Field1”, Field2”, etc. so that control data sources wouldn’t have to be changed. Controls that aren’t used could be made invisible. This would require a lot of code.
4. Have each stage as a subform and just edit the visibility status of each form as needed. Might have to resize and change the location of each subform as they are made visible.
Like I said, this is new to me and these are just the ideas that came to me. Criticism of any or all of my ideas is welcome. I believe that I can implement each of these solutions, so exact details aren’t needed, just which path I should take. If I stumble on the chosen path, I will post that separately.
Comment