Hi folks,
Hoping that like always you fine folks can help me figure this out.
I'm trying to set up a form (basic, bound single form used for both entering new data and updating existing records) where only the top control is enabled to begin with, and each control below this is only enabled when the data from the controls above has been filled in.
Eg, no skipping down the page until you've entered everything in sequence.
Thinking of something in the BeforeUpdate that to toggle the "Enabled" property of the "next" control to True.
"Next" is kind of a tricky construct: thinking of using the tab stop index as a proxy for this? Any other ideas? I'd like to make this somewhat generalizable so want to avoid just hardcoding the order into the process.
Had also considered putting it into the form's BeforeUpdate instead, and looping through each control, enabling only the controls that already have data entered + 1 more (in the tricky-to-define sequence mentioned above). Better, worse, or indifferent solution in all your expert opinions?
I think I'd need something to set the initial state of enabled/disabled fields outside the control level anyway as people do use this to update existing records too, so they could move to a new record before completing an old one.
That's totally fine, I just don't want any blanks in the record for our audit trail, as each field is documenting a particular process step.
Would appreciate any input you guys have to offer on this.
Hoping that like always you fine folks can help me figure this out.
I'm trying to set up a form (basic, bound single form used for both entering new data and updating existing records) where only the top control is enabled to begin with, and each control below this is only enabled when the data from the controls above has been filled in.
Eg, no skipping down the page until you've entered everything in sequence.
Thinking of something in the BeforeUpdate that to toggle the "Enabled" property of the "next" control to True.
"Next" is kind of a tricky construct: thinking of using the tab stop index as a proxy for this? Any other ideas? I'd like to make this somewhat generalizable so want to avoid just hardcoding the order into the process.
Had also considered putting it into the form's BeforeUpdate instead, and looping through each control, enabling only the controls that already have data entered + 1 more (in the tricky-to-define sequence mentioned above). Better, worse, or indifferent solution in all your expert opinions?
I think I'd need something to set the initial state of enabled/disabled fields outside the control level anyway as people do use this to update existing records too, so they could move to a new record before completing an old one.
That's totally fine, I just don't want any blanks in the record for our audit trail, as each field is documenting a particular process step.
Would appreciate any input you guys have to offer on this.