Makes a lot of sense to me Mark. I wrote an app under 5.0 a few years back where the user had to be led through a complicated financial posting, so we did it Wizard style, with each page progressively activating, disabling the others.

>
>Aside from the other replies, I would think the user-friendly way to do this is to deactivate any pages not currently available to the users. As an example, one of my forms has a 3 page pageframe and pages 2 and 3 only activate if applicable. The first page has some generic user access authorities [e.g. read-only access to the customers table]. If the user is granted RO to the customer table, page 2 activates so table level options can be set. For example, if the user is then granted edit privileges on the customer table, page 3 is activated where field level privileges can be set.