>Steve,
>
>You deserve a head start:) . Take a look at my deBase class, the base class of my dataenvironment class. The inherited classes are instantiated by the load method of forms. This is done at the base level as well.
>
>As you see it enables you to (1) clone a table if that is what you want, or combine fields from open tables (mind you the DE is responsible for opening the tables) or create you fields by supplying the type you require. (I admit that the name of the method could have been a bit shorter, but that is nothing a good macro cannot solve!).
>
>What you do after that is entirely up to you. You can populate it with empty records and submit that to a grid, or you can bind controls in your form to a one record cursor.
>
>HTH,
>
>Marc

Marc,

I've cut the code and will look at it. THANKS!! And just to let you know that I too was thinking about what you said earlier.....I went out over the weekend and developed something that now looks strikingly like what you just put here. It has become my data maintenance mgr and handles all the forms for that purpose.

It does just what you've done, create an array of field info and manipulates that. Works rather well. I'm going to look at your code and see if there is something that I can add to it and work on incorporating it elsewhere.

Thanks again,
Steve