Perhaps your "50 fields" should be 25 or 50 records instead of fields all in one record.
I don't see why a single submit button on the form, not the slider, can't be used to check for completeness. This would not prevent the student from going back to previous questions and modifying their answer until they click that final submit button. Clicking submit can even pop up an "are you sure you are done?" confirmation dialog before actually ending the test.
I'd be tempted to go with solution 2 and use a loop with a "go to next field" step. This would require you to manage the tab order of the fields in question, but with this solution, you could capture the field name from whatever field triggers the "not IsEmpty" if statement.
@Phil - I would like to use a single submit button and check for completeness. I'll have to experiment and set the account access for the related table as well. (if you'd remember from my previous post about setting up account access to limit users to their own record only).
@ Matthew. That sounds like a workable solution without creating another table. I'm still new to FM so things that may be obvious aren't so to me. I am managing the tab order because this will be viewed on an iPad. For usability purposes I wouldn't want the tab order to be all over the place when entering information. I'll give it a try. Thanks!
(if you'd remember from my previous post about setting up account access to limit users to their own record only).
Taking a test and completing a survey is much the same process except that a test has right and wrong answers. You may find this thread on questionaires and surveys helpful in how to best design the tables and relationships of such a database: Need aid on generating a report from a survey layout.