>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). Anyway, the higher authorities have decided that real solution is to allow each user who has design rights to design the screen themselves, picking and choosing which fields should be displayed, and in what order.
>
>So, my question is not so much how do I do this, although if you've got the silver bullet, I'd take it, but really is there any reading material, or starting point I should be looking at. The application is currently done in VFP 6 with Stone Field Queries and SDT, 1 DBC and about 30 differnt tables. My background is in using the Power Tools to draw the forms, now I think I'm going to turn into a VB programmer and have to right tons of createobject code.
>
>Thanks for any and all input.
>Kirk

I think Mike Antonovich has the right idea. Man is this going to be a pain on the frontend! I think you can pull it off if you really do your homework. My guess is you need to have this ALL data driven. My guess is that each group would have its own list of possible fields. If this is true you won't have to care about what order they are in because you can all so have a dbf that hold the mandintory list of fields and the validation for those fields. Depending on the group they are in, have a dbf that contains the files needed for that group and have the load of the form(s) handle that. Once they have built there layout save all to a local dbf but make a copy on a server. That way you can trouble shoot by using thier profile and they could, if you got really cute, have a roaming type profile.

This would really be a TUFF thing to pull off, but man what a great way to improve productivity of the users.


Jeff