-----Original Message-----
Hi HKM,
In my opinion does this something as a copy a datatable and does not create
a new table in a database.
Yah, to be precise selective copy with column datatype
translation forced onto underlying layer.
But maybe was that what was wanted and did I understand
it wrong.
?
(The methode to do that is much easier by the way. When
it is a complete table you can do copy)
MY problem was, I construct TABLE A by reading bunch of
delimited text files. Now ODBC/JET drivers are really not
intelligent enough to understand the datatypes on most of
the cases. On the top of this, my target schema in the
database is not flexible to accept numbers in the text
format. Next point is , you cannot change TABLE A column
datatypes once it has data. This forced me into situation
where I'll create a typed dataset with schema from the
database and feed data into [row][column] fashion. This
implementation then delegates the responsibility of
conversion of text data into respective format as that of
target table in the database.
And when it is a part you can do a for loop thru the
rows with a copy of a
selected sets of items. If that are a lot, you can place that in a simple
array, therefore you do not need a hastable.
ACtually hashtable just holds that column name that needs
to be transfered to target table. I needed a lookup
mechanism since I want to upload selected columns only. So
when u come across column x in the TABLE A (build by
reading text files) all you do is just check if current
column is there in the target schema if yes then copy the
data otherwise dont.
Thanks,
-HKM