Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
SQL
ce
clients
clustering
connect
datamining
datawarehouse
dts
fulltext
jdbcdriver
msde
mseq
newusers
notificationsvcs
odbc
olap
programming
replication
reportingsvcs
security
securitytools
server
setup
sqlxml.viewmapper
tools
xml
  
 
date: Sat, 20 Sep 2008 08:57:00 -0700,    group: microsoft.public.sqlserver.dts        back       


SSIS Script Component Output Columns Integer only   
Hi

I am in Microsoft Visual Studio 2005 - Business Intelligence Project - SSIS 
package.
I have my Excel data sitting in a global variable as an object. It is there 
in one row, with only the column headings as I require.

I can create the script component with the source option to convert the 
columns into rows, and output them - ok all works.

What I can't get to happen is to make the output rows anything other than 
int for the simple reason everytime I go into the output columns for that 
column the datatype drop down box is blacked out. 

Anyone have a clue what is going on, I'll be bald soon.

Marc
date: Sat, 20 Sep 2008 08:57:00 -0700   author:   Marc in Oz Marc in

Re: SSIS Script Component Output Columns Integer only   
On Sep 21, 1:57 am, Marc in Oz <Marc in
O...@discussions.microsoft.com> wrote:
> Hi
>
> I am in Microsoft Visual Studio 2005 - Business Intelligence Project - SSIS
> package.
> I have my Excel data sitting in a global variable as an object. It is there
> in one row, with only the column headings as I require.
>
> I can create the script component with the source option to convert the
> columns into rows, and output them - ok all works.
>
> What I can't get to happen is to make the output rows anything other than
> int for the simple reason everytime I go into the output columns for that
> column the datatype drop down box is blacked out.
>
> Anyone have a clue what is going on, I'll be bald soon.
>
> Marc

Hi,
The next day I tried again on a small test project, and that drop down
was working.
So I went back in the main project, and it was there and settable.
So, if this was a resource problem, would it not be preferable to get
a 'low on resources' error?
Any clue would be good
thx
Marc
date: Sun, 21 Sep 2008 16:30:05 -0700 (PDT)   author:   unknown

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us