>>Hey Bob, this is a neat way to handle this! What I like to do is use a custom class as a wrapper to my SCATTER NAME object. The wrapper creates it, keeps track of the table name, field types, unique id, a recno() & reccount() if necessary, plus it has a basic loop thru table method that I havent really needed much since I added it. Same idea I think, except I never make use of AddProperty, and the name value I give SCATTER NAME is meaningless (SUBSTR(SYS(2015), 3, 10) ).
>
>I may give your method a try to see how it works. There are so many options available to accompish the same result! I have been considering adding table schema info to mine but haven't really found a need (yet! :>) ).

One thing I like about the way I do it is the wrapper object is my window into what's happening if I'm in the debugger.... I never could figure out how to see my SCATTER NAME object in the watch/locals debug windows (errr... back in VFP 5 come to think about it), so I use the wrapper object to manage it & tell me what's going on.