I've seen this done once before. It involved first a configuration screen to let a user select which fields they could see. This information was saved in a separate configuration table. The order of the records would later determine the order in which the fields were displayed. Also each field had a width, height, and control type associated with it in a second table. Then the form was opened empty except for navigation and control buttons at the bottom. The INIT of the form read the configuration table to find which fields were needed and then added the controls to the form. Using height and width factors stored with each field (as well as control type), the program 'built' the form from the top down. It was not especially pretty, but it did allow each user to have a custom form.

HTH.

>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