Kevin,

A method that I have used in the past with VFP was to have the forms textboxed disabled (so no accidental editing could take place) and the user would have to click on EDIT to actually change anything and they Click on SAVE to save the data. When the person would click on the EDIT button - I would enable any fields that the user (based on a security table) was allowed to change. I would do this by stepping through the controls and fields. By having the textboxes, cbo's etc disabled to start with - they I only have to run the loop through the fields when they choose to EDIT - not on every click of next or previous. (This is a user that want the older type of controls of top, previous etc).

What I have done in the past with VFP was to subclass the textboxes and have all of their readonly values set to .T..

I had then seen some frameworks that would look for a field in a setup table or config file and would automaticly set the textboxes etc as readonly or not.

I guess that was what I was wondering if MM had -- prior to my going though and subcalassing the textboxes etc. or having to loop through on every next, previous to disable fields.

Appreciate the help

Darrell