Form Planning

[stevenblanc]

Hey folks,

Does anyone have any resources on form planning? I keep revising my forms to make them more streamlined and then I discover new features that demand reorganization.

Right now I'm trying to determine the best way to build a form with Add/Remove/Edit capabilities with an efficient navigation system. Just looking for some inspiration. Add/remove on one form with records loaded to list boxes and a second form to load the full record for editing? A header above the listbox for editing?

Anyone have a sample cache I can flick through for user flow?

Cheers,

Steven

 

[mdlueck]

I keep revising my forms to make them more streamlined and then I discover new features that demand reorganization.

Excellent!

Right now I'm trying to determine the best way to build a form with Add/Remove/Edit capabilities with an efficient navigation system. Just looking for some inspiration. Add/remove on one form with records loaded to list boxes and a second form to load the full record for editing? A header above the listbox for editing?

In that case I will offer you...

Client/Server Architecture
http://www.access-programmers.co.uk/forums/showpost.php?p=1110794&postcount=5

In general, working very transactionally will have you developing a reliable / consistent application. Using a RDBMS as a Spreadsheet will find you chasing obscure / difficult bugs. Example, allowing a Multiple Items form to be editable. Instead select a record in the Multiple Items form, bring that record into edit mode. If Commit / Save button is used to exit the form, Commit the values back to the DB. If Rollback / Cancel button is used, nothing happens to the database / changes are destroyed.

 

[Simon_MT]

I put all my data into continous foms on Review Screens , generally with no Editing. Then if you want to Add / Edit / Delete there is a separate Entry Form, you then decide whether or not users can delete records.

Simon

 

[stevenblanc]

Well I'm thinking of rebuilding the database from scratch at this point.

I'll start by building a user system with either, userlevels, or action lists to determine which actions users are allowed to perform.

I'm then thinking to make start on a home form with a header menu across the top and two sub forms below. The left subform designated as an unmoving navigation form. the right subform designated to be the review pane (courses, faculty, etc) which will contain listboxes displaying all records from a particular table.

The navigation pane will dictate which form is loaded into the right subform. Record removing actions if available will occur within the review pane. Popup forms to be loaded for add/edit actions.

All review panes should also have filter and sort options and the ability to export full tables to excel. I do not expect the organization to exceed excels row limit for a number of years so I can drag that out for a bit.