How can i preserve data type during the export to Excel

When i export data to a Excel file numeric fields are exported as
General type in excel.
Does anybody know how can i preserve numeric type for this columns
(double, float or integer).On 30.10.2006 12:00, Sale wrote:
> When i export data to a Excel file numeric fields are exported as
> General type in excel.
> Does anybody know how can i preserve numeric type for this columns
> (double, float or integer).
>
How do you export them? Did you try to import them from Excel directly
via ODBC data source?
robert|||> How do you export them? Did you try to import them from Excel directly
> via ODBC data source?
> robert
I use DTS package for export to Exel|||Maybe better question is wich data type Excel accept as number when i
perform export from SQL server ( via DTS). I tried double (SQL offer
this as a default), and decimal, but result remain the same.

How can i preserve data type during the export to Excel

When i export data to a Excel file numeric fields are exported as
General type in excel.
Does anybody know how can i preserve numeric type for this columns
(double, float or integer).On 30.10.2006 12:00, Sale wrote:
> When i export data to a Excel file numeric fields are exported as
> General type in excel.
> Does anybody know how can i preserve numeric type for this columns
> (double, float or integer).
>
How do you export them? Did you try to import them from Excel directly
via ODBC data source?
robert|||> How do you export them? Did you try to import them from Excel directly
> via ODBC data source?
> robert
I use DTS package for export to Exel|||Maybe better question is wich data type Excel accept as number when i
perform export from SQL server ( via DTS). I tried double (SQL offer
this as a default), and decimal, but result remain the same.

How can I import txt files using fdf field info ??

I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
Server database. They were apparently exported from SAP, and each came with
a corresponding fdf file that lists the field layout information ...
PCFDF
PCFT 1
PCFO 1,1,1,1,1
PCFL YR 1 2
PCFL DIV 1 18
...
PCFL E12 2 13/3
Is there any way that I can get Enterprise Manager to use this information,
rather than forcing me to enter it manually ? Alternatively, is there a
third party app that'll do that ? The layouts are not necessarily
identical for all the files, so I really need to use the information from
each file's corresponding fdf.
Thanks
--
Jim Cook
jimcook@.panix.com.no.spamJim
you can easily import text files. withEM
EM> right click on Data Transformation services > import data and give path
of .txt
This is abt txt. I dont know about sap
Regards
R.D
"Jim Cook" wrote:
> I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
> Server database. They were apparently exported from SAP, and each came with
> a corresponding fdf file that lists the field layout information ...
> PCFDF
> PCFT 1
> PCFO 1,1,1,1,1
> PCFL YR 1 2
> PCFL DIV 1 18
> ...
> PCFL E12 2 13/3
> Is there any way that I can get Enterprise Manager to use this information,
> rather than forcing me to enter it manually ? Alternatively, is there a
> third party app that'll do that ? The layouts are not necessarily
> identical for all the files, so I really need to use the information from
> each file's corresponding fdf.
> Thanks
> --
> Jim Cook
> jimcook@.panix.com.no.spam
>|||Yes, I've done that - but the wizard gets to a window where it wants me to
click where each field ends and the next begins. I have that information in
the fdf files, but I do not want to go through the process of defining ~100
field spans for ~20 files. I strongly suspect that the fdf files were
created by SAP during the export operation, but they're apparently not
recognized by EM as proper import templates. So what I'm looking for is an
app that converts the fdf files to EM's import template format, or natively
uses fdf files in doing SQL Server imports. I've done a fair amount of
googling, and have found leads re using fdfs in MySQL imports, but nada re
SQL Server imports.
--
Jim Cook
jimcook@.panix.com.no.spam
"R.D" wrote:
> Jim
> you can easily import text files. withEM
> EM> right click on Data Transformation services > import data and give path
> of .txt
> This is abt txt. I dont know about sap
> Regards
> R.D
>
> "Jim Cook" wrote:
> > I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
> > Server database. They were apparently exported from SAP, and each came with
> > a corresponding fdf file that lists the field layout information ...
> >
> > PCFDF
> > PCFT 1
> > PCFO 1,1,1,1,1
> > PCFL YR 1 2
> > PCFL DIV 1 18
> > ...
> > PCFL E12 2 13/3
> >
> > Is there any way that I can get Enterprise Manager to use this information,
> > rather than forcing me to enter it manually ? Alternatively, is there a
> > third party app that'll do that ? The layouts are not necessarily
> > identical for all the files, so I really need to use the information from
> > each file's corresponding fdf.
> >
> > Thanks
> > --
> > Jim Cook
> > jimcook@.panix.com.no.spam
> >

How can I import txt files using fdf field info ??

I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
Server database. They were apparently exported from SAP, and each came with
a corresponding fdf file that lists the field layout information ...
PCFDF
PCFT 1
PCFO 1,1,1,1,1
PCFL YR 1 2
PCFL DIV 1 18
...
PCFL E12 2 13/3
Is there any way that I can get Enterprise Manager to use this information,
rather than forcing me to enter it manually ? Alternatively, is there a
third party app that'll do that ? The layouts are not necessarily
identical for all the files, so I really need to use the information from
each file's corresponding fdf.
Thanks
Jim Cook
jimcook@.panix.com.no.spam
Jim
you can easily import text files. withEM
EM> right click on Data Transformation services > import data and give path
of .txt
This is abt txt. I dont know about sap
Regards
R.D
"Jim Cook" wrote:

> I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
> Server database. They were apparently exported from SAP, and each came with
> a corresponding fdf file that lists the field layout information ...
> PCFDF
> PCFT 1
> PCFO 1,1,1,1,1
> PCFL YR 1 2
> PCFL DIV 1 18
> ...
> PCFL E12 2 13/3
> Is there any way that I can get Enterprise Manager to use this information,
> rather than forcing me to enter it manually ? Alternatively, is there a
> third party app that'll do that ? The layouts are not necessarily
> identical for all the files, so I really need to use the information from
> each file's corresponding fdf.
> Thanks
> --
> Jim Cook
> jimcook@.panix.com.no.spam
>
|||Yes, I've done that - but the wizard gets to a window where it wants me to
click where each field ends and the next begins. I have that information in
the fdf files, but I do not want to go through the process of defining ~100
field spans for ~20 files. I strongly suspect that the fdf files were
created by SAP during the export operation, but they're apparently not
recognized by EM as proper import templates. So what I'm looking for is an
app that converts the fdf files to EM's import template format, or natively
uses fdf files in doing SQL Server imports. I've done a fair amount of
googling, and have found leads re using fdfs in MySQL imports, but nada re
SQL Server imports.
Jim Cook
jimcook@.panix.com.no.spam
"R.D" wrote:
[vbcol=seagreen]
> Jim
> you can easily import text files. withEM
> EM> right click on Data Transformation services > import data and give path
> of .txt
> This is abt txt. I dont know about sap
> Regards
> R.D
>
> "Jim Cook" wrote:

How can I import txt files using fdf field info ??

I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
Server database. They were apparently exported from SAP, and each came with
a corresponding fdf file that lists the field layout information ...
PCFDF
PCFT 1
PCFO 1,1,1,1,1
PCFL YR 1 2
PCFL DIV 1 18
...
PCFL E12 2 13/3
Is there any way that I can get Enterprise Manager to use this information,
rather than forcing me to enter it manually ? Alternatively, is there a
third party app that'll do that ? The layouts are not necessarily
identical for all the files, so I really need to use the information from
each file's corresponding fdf.
Thanks
--
Jim Cook
jimcook@.panix.com.no.spamJim
you can easily import text files. withEM
EM> right click on Data Transformation services > import data and give path
of .txt
This is abt txt. I dont know about sap
Regards
R.D
"Jim Cook" wrote:

> I have many ca. 1-5 Gb fixed field width txt files to import into a SQL
> Server database. They were apparently exported from SAP, and each came wi
th
> a corresponding fdf file that lists the field layout information ...
> PCFDF
> PCFT 1
> PCFO 1,1,1,1,1
> PCFL YR 1 2
> PCFL DIV 1 18
> ...
> PCFL E12 2 13/3
> Is there any way that I can get Enterprise Manager to use this information
,
> rather than forcing me to enter it manually ? Alternatively, is there a
> third party app that'll do that ? The layouts are not necessarily
> identical for all the files, so I really need to use the information from
> each file's corresponding fdf.
> Thanks
> --
> Jim Cook
> jimcook@.panix.com.no.spam
>|||Yes, I've done that - but the wizard gets to a window where it wants me to
click where each field ends and the next begins. I have that information in
the fdf files, but I do not want to go through the process of defining ~100
field spans for ~20 files. I strongly suspect that the fdf files were
created by SAP during the export operation, but they're apparently not
recognized by EM as proper import templates. So what I'm looking for is an
app that converts the fdf files to EM's import template format, or natively
uses fdf files in doing SQL Server imports. I've done a fair amount of
googling, and have found leads re using fdfs in mysql imports, but nada re
SQL Server imports.
Jim Cook
jimcook@.panix.com.no.spam
"R.D" wrote:
[vbcol=seagreen]
> Jim
> you can easily import text files. withEM
> EM> right click on Data Transformation services > import data and give pat
h
> of .txt
> This is abt txt. I dont know about sap
> Regards
> R.D
>
> "Jim Cook" wrote:
>