Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Excel Destination.

Status
Not open for further replies.

joejack0330

Technical User
Jan 27, 2006
95
US
Trying to export from sql 2005 to excel file and after finally getting all the transformations working because unicode and non-unicode issues, I've hit a problem that I can't seem to find any help on. When I run the following in Excel destination task, it changes the '#' in the File # column heading to a '.' I've tried different variations but no good and if I open created excel file, it lets me change the column heading with # so don't think it's excel itself. The partner that we are sending data to requested it with that column name trying to make it work for them. Here is the create table from the excel destinaton.
CREATE TABLE `Excel Destination` (
`Co Code` NVARCHAR(3),
`Batch ID` INTEGER,
`File #` INTEGER,
`Temp Dept` NVARCHAR(5),
`Reg Hours` NUMERIC (5,2),
`O/T Hours` NUMERIC (5,2),
`Hours 3 Code` NVARCHAR(2),
`Hours 3 Amount` NUMERIC (5,2)
)

But this is how it looks in excel.

Co Code Batch ID File . Temp Dept Reg Hours

etc...

Thanks,
Joe
 
Update: It looks like that was not the only problem because does not seems to overwite or create new file easily when runing more than once without having to go back into package. But, good news is if I create a template file and using system task to copy template over to my OP destination name, it works. I just created my template with correct column headers and can get around the # problem. You would think going from one Microsoft product to another would be easier! Thanks, Joe
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top