>We currently have a project that uses lots of forms and pageframes to display all the possible information. Problem is, different groups use different fields, not all fields are required, so shouldn't be viewed by others, and they just aren't happy until they get it their way (I guess they heard I was a fry cook at burger king).

One whopper with fries to go and cut the sauce!

If you are allowed to present lists using a GRID structure then here is a cheap trick that would let you get away with writing only one form.
1) Create a form
2) Attach a grid
* Record source = alias
* Alias name = [YourAlias] && What ever
3) Define a field restriction macro
FieldsForUserType1=[ Name, Address, Phone]
FieldsForUserType2=[ Name, Phone, Bal_forward]

Then in the GRIDS Load event (and dependent on your field restrictions)
select YourAlias
**Then dependent on you user restrictions**
SET FIELDS to &FieldsForUserType1 && For user type1
..or
SET FIELDS to &FieldsForUserType2 && ditto
.. or

You could use a List solution that would render the TextBox Visible to .F., should the user not need to view a particular field.

One key to developing with VFP is acquiring the confidence that you can literally do anything you need (or imagine) in fairly short order. It's also nice to have a UT membership!