>You can use a SELECT...UNION to not have to filter the field names.
>

Great idea! What does it do if you have two fieldnames that are the same, but the field definitions are different? Is there a way of prediciting which will be selected, or will both be present since the records aren't identical. (ie one might be N(8,0) and the other I, or worse, one character and the other a numeric type)

>Vlad
>
>>You'll need to filter out any duplicated field names, but this should give you a starting point.