I am attempting to use a wizard approach for the input of data into my database. I have a master form and it contains a subform. The subform changes as the operator navigates through the wizard. I change the subform by changing the SourceObject of the subform to another subform.
However, one of my problems is that the table fields are required and when I "navigate" to the next page, I get a required field is unanswered message from access. The next page in the wizard will be where more required fields will be answered (typed in).
In other words, I don't want to commit the record until the the last page of the wizard and all required info has been provided.
The reason I want a wizard is because there is so much info that pertains to the main table and I would like the operator to enter the info in a logical flow.
I have another problem with this approach, each Subform has DataEntry set to Yes, so as I go backward in the wizard to view already entered data, all fields have been blanked. If I change the DataEntry to No, then I cycle through records that already exist in my database. My question is how do I maintain the New(current) record in this wizard approach?
Have you ever developed a wizard like this? Is it a good design?
Do you have an example of this?
However, one of my problems is that the table fields are required and when I "navigate" to the next page, I get a required field is unanswered message from access. The next page in the wizard will be where more required fields will be answered (typed in).
In other words, I don't want to commit the record until the the last page of the wizard and all required info has been provided.
The reason I want a wizard is because there is so much info that pertains to the main table and I would like the operator to enter the info in a logical flow.
I have another problem with this approach, each Subform has DataEntry set to Yes, so as I go backward in the wizard to view already entered data, all fields have been blanked. If I change the DataEntry to No, then I cycle through records that already exist in my database. My question is how do I maintain the New(current) record in this wizard approach?
Have you ever developed a wizard like this? Is it a good design?
Do you have an example of this?