Very Computer

>DTS is designed to use the DTS Flat file driver that ships with it, not the
>ODBC flat file driver.

>> When i try to transform an Excel file to a flat file associated to a
>> Microsoft Text Driver (ODBCJT32.dll ver 4.00.3513 ) i get the following
>> error:

>> Error at Destination for Row number 1. Errors encountered so far in this
>> task: 1.
>> Error Source: Microsoft OLE DB Provider for ODBC Drivers
>> Error Description:The query is not updateable because
>> the from clause is not a single simple table name.

>> Have you any suggestion?
>> Thanks in advance
>> Mike

>DTS is designed to use the DTS Flat file driver that ships with it, not the
>ODBC flat file driver.

>> When i try to transform an Excel file to a flat file associated to a
>> Microsoft Text Driver (ODBCJT32.dll ver 4.00.3513 ) i get the following
>> error:

>> Error at Destination for Row number 1. Errors encountered so far in this
>> task: 1.
>> Error Source: Microsoft OLE DB Provider for ODBC Drivers
>> Error Description:The query is not updateable because
>> the from clause is not a single simple table name.

>> Have you any suggestion?
>> Thanks in advance
>> Mike

> Ok! I decided to use the ODBC Flat file driver 'cause it mantains the
names
> of the columns of my file (I have an odbc definition contained in a
> schema.ini file; the file is "|" separated). If I use ODBC driver during a
> DTS transformation I can see the names of the file's columns; but if I use
> DTS Flat file driver I can't see the names of the columns and the mapping
> task is hard! DTS Flat text driver seems not to see any schema.ini
> Thanks
> Regards

> >DTS is designed to use the DTS Flat file driver that ships with it, not
the
> >ODBC flat file driver.

> >> When i try to transform an Excel file to a flat file associated to a
> >> Microsoft Text Driver (ODBCJT32.dll ver 4.00.3513 ) i get the following
> >> error:

> >> Error at Destination for Row number 1. Errors encountered so far in
this
> >> task: 1.
> >> Error Source: Microsoft OLE DB Provider for ODBC Drivers
> >> Error Description:The query is not updateable because
> >> the from clause is not a single simple table name.

> >> Have you any suggestion?
> >> Thanks in advance
> >> Mike

>The flat file OLEDB doesn't use a separate schema.ini file. It can read
>column names from the front of the data file (comma separated) if you
>specify that.

>> Ok! I decided to use the ODBC Flat file driver 'cause it mantains the
>names
>> of the columns of my file (I have an odbc definition contained in a
>> schema.ini file; the file is "|" separated). If I use ODBC driver during
a
>> DTS transformation I can see the names of the file's columns; but if I
use
>> DTS Flat file driver I can't see the names of the columns and the mapping
>> task is hard! DTS Flat text driver seems not to see any schema.ini
>> Thanks
>> Regards

>> >DTS is designed to use the DTS Flat file driver that ships with it, not
>the
>> >ODBC flat file driver.

>> >> When i try to transform an Excel file to a flat file associated to a
>> >> Microsoft Text Driver (ODBCJT32.dll ver 4.00.3513 ) i get the
following
>> >> error:

>> >> Error at Destination for Row number 1. Errors encountered so far in
>this
>> >> task: 1.
>> >> Error Source: Microsoft OLE DB Provider for ODBC Drivers
>> >> Error Description:The query is not updateable because
>> >> the from clause is not a single simple table name.

>> >> Have you any suggestion?
>> >> Thanks in advance
>> >> Mike

>When the destination is a flat file, it gets column names from the file
>definition in the transformation. In the wizard, you would click on the
>Transform button on the Select Destination File Format dialog and change
the
>names of the destination columns. In the Designer, you change the
>destination column names in the destination tab of the transform (click
>new).
>- Bill

>> Thank you for your precious suggestion and help.
>> In my environment when I use a DTS flat file as Destination I can't see
>the
>> names of the columns: DTS tries always to create in the destination file
>the
>> same columns of the Source and seems not to see the column definition in
>the
>> front of the file.
>> Instead, all seems to work as you wrote when I use a Source Flat file.
>> Where is my mistake?
>> Thanks

> Why Destination Flat file driver does not keep the columns names put in
> front of file? They help to correctly mapping the fields, so that the data
> consumer of that file (another cobol program) will find the fields it
> expects.
> Thank you for your great help!

> >When the destination is a flat file, it gets column names from the file
> >definition in the transformation. In the wizard, you would click on the
> >Transform button on the Select Destination File Format dialog and change
> the
> >names of the destination columns. In the Designer, you change the
> >destination column names in the destination tab of the transform (click
> >new).
> >- Bill

> >> Thank you for your precious suggestion and help.
> >> In my environment when I use a DTS flat file as Destination I can't see
> >the
> >> names of the columns: DTS tries always to create in the destination
file
> >the
> >> same columns of the Source and seems not to see the column definition
in
> >the
> >> front of the file.
> >> Instead, all seems to work as you wrote when I use a Source Flat file.
> >> Where is my mistake?
> >> Thanks