Loading Exported in Excel format data into SQL Server
Loading Exported in Excel format data into SQL Server
(OP)
Please forgive any ignorance here but I am not a user of Seagate.
We are using Seagate Info 7.5 to create a file to be imported into SQL server 7. Due to a limitation within Seagate to do with Sub-Reports we cannot use a CSV file and the only viable option is to export in Excel format. The file produced appears to be fine but neither SQL Server's Data Transformation Services nor Microsoft's Access will read the file. The file will open in Excel and if it is then saved it will load into SQL Server or Access without issue.
I have reported this to Crystal Decisions but, as we purchased through a VAR, we are experiencing difficulty in obtaining support and I was wondering if anyone else has come across this issue.
Thanks in anticipation.
John
We are using Seagate Info 7.5 to create a file to be imported into SQL server 7. Due to a limitation within Seagate to do with Sub-Reports we cannot use a CSV file and the only viable option is to export in Excel format. The file produced appears to be fine but neither SQL Server's Data Transformation Services nor Microsoft's Access will read the file. The file will open in Excel and if it is then saved it will load into SQL Server or Access without issue.
I have reported this to Crystal Decisions but, as we purchased through a VAR, we are experiencing difficulty in obtaining support and I was wondering if anyone else has come across this issue.
Thanks in anticipation.
John
Talk To Other Members
RE: Loading Exported in Excel format data into SQL Server
Does it give an error?
I haven't worked with SI for quite some time, are there different Excel export options?
Perhaps a SP or Hotfix can help, check:
http://support.crystaldecisions.com/library/kbase/articles/c2009496.asp
-k
RE: Loading Exported in Excel format data into SQL Server
The situation is more complicated with SQL Server as, if an existing DTS package is used which would be the norm, the read fails with messages indicating that the named worksheet cannot be found. If a new package is created using the 'invalid' file, this succeeds but when executed no conversions are actually achieved although no errors are produced. It just appears to skip all the data!
I feel sure that if Access will read the file correctly then SQL Server will as well.
Any additional assitance would be much appreciated. In the meantime I will check the position in regard to hot fixes and the like.
Reagards.
John