>>>But then you would have to have ALL columns of the table into the CA (which is fine but not always necessary). Another thing to take into account is that the Types in SQL Server are different from those in VFP and when constructing the CursorSchema some type "translations" should be done. Which is also not insurmountable. Another thing is sometimes you want to have a column or two from a child table so this complicates things.
>>>
>>>I just wish that I could use CA without CursorSchema and could simply specify that all DateTime types to be converted to Date type and Varchar(MAX) to memo. This would satisfy 99.99% of my needs. But I don't think it is possible.
>>
>>You can alternatively create a table (or XML) in VFP and get the info initially from that view and then drop non used columns and adjust some fields. That may be better for your purposes.
>>
>
>This is exactly the reason I started this thread is to see what would be a better choice for meta table, XML, DBF, or SQL Table.
>
>By the way, in your first reply you used "schema_name"; I believe it should be "table_schema"

You're right - mistyped.

Either way will work - DBF may be the simplest to implement.

Or probably XML - so it will be external config file.

SQL table will work too.

In other words, each will work - it's a matter of personal preference.