I have posted an html of my table list and table field details. Please feel free to view this to help in understanding what I have created in the backend, which serves the forms front-end.
http://www.geocities.com/misscrf/tabledefinitions.html
I am currently struggling to get my entry form to work in an end user friendly manner. I want to make sure that a basic end user can come in and navigate through the form, and not be compelled to leave out information.
One thing to explain, about my current setup, is why the address subform, phone subform and application subform look different.
I have the address subform as a single form with navigation buttons. If the candidate (applicant) has more than one address then they use the navigation buttons. The problem is that when they tab from the zip, the first record is no longer seen, and the user doesn't understand what happend to the first address.
I have attached a zip with screen shots of my forms. ( The db is too big to post, even without data) It shows the main menu, and then the entry form. There is one shot for the entry form showing each page/subform tab. I would love any thoughts on how I should best control this and make it end user friendly while ensuring data is inputed correctly.
The phone subform is set as continous. So what you see in the screen shots, is that once a phone type is chosen, a second record begins to show, for input.
I am not sure which is better or how I should set these subforms up. The application tab shows as a single form with previous and next application buttons. I forgot that I would need a new application button. I don't know if that is the method I should use.
Whichever may be best, I believe I should make it the same for all tabs. The phone, address, and application tabs should all operate the same. The challenge comes when deciding how the activities, inside the applications, should work.
I look forward to any useful suggestions for setting this up as best as possible.
http://www.geocities.com/misscrf/tabledefinitions.html
I am currently struggling to get my entry form to work in an end user friendly manner. I want to make sure that a basic end user can come in and navigate through the form, and not be compelled to leave out information.
One thing to explain, about my current setup, is why the address subform, phone subform and application subform look different.
I have the address subform as a single form with navigation buttons. If the candidate (applicant) has more than one address then they use the navigation buttons. The problem is that when they tab from the zip, the first record is no longer seen, and the user doesn't understand what happend to the first address.
I have attached a zip with screen shots of my forms. ( The db is too big to post, even without data) It shows the main menu, and then the entry form. There is one shot for the entry form showing each page/subform tab. I would love any thoughts on how I should best control this and make it end user friendly while ensuring data is inputed correctly.
The phone subform is set as continous. So what you see in the screen shots, is that once a phone type is chosen, a second record begins to show, for input.
I am not sure which is better or how I should set these subforms up. The application tab shows as a single form with previous and next application buttons. I forgot that I would need a new application button. I don't know if that is the method I should use.
Whichever may be best, I believe I should make it the same for all tabs. The phone, address, and application tabs should all operate the same. The challenge comes when deciding how the activities, inside the applications, should work.
I look forward to any useful suggestions for setting this up as best as possible.
