>This is very similar to ADO and a wrapper around the ADO object would handle this quite nicely, except that there would be some duplication. In the ADO Object model you have a record set object, the record set object contains a fields collection and then the field objects have value, original value and underlying value properties. IOW, the three possible uses for SCATTER NAME that you've outlined are provided in ADO. We've got classes in our Tahoe version of VFE that mimic this behavior, sort of in anticipation of supporting ADO. If you think ADO is in your future adopting what you've already done to the ADO interface should be a piece of cake. Of course if you want to just send me a check that's fine too. :-)
>
>Does your setcontrolsources? method have to be coded manually for each form or do you have some technique you're using for matching controls with the SCATTER NAME values?

Matching algorithm itself depends on client requirements (if any) how to handle multi-user save collisions and I code it manually. I am quite aware that some common technique would be suitable, but I just didn't have chance to work on it.