Rather than listing your variables in the Read Only section of the component, you will almost certainly have more success by using VariableDispenser to read them.

I can post an example...

I suggest that you import your data as two columns: Name, TheRest and add a derived column transformation, ClockNum, which is defined as Left(TheRest, 5).

Phil

Declare @month int, @year int

Declare @dt Datetime

Set @dt = getdate()

set @month = month(@dt) - 1

set @year = year(@dt)

if @month = 0 --january

begin

Set @month = 12

Set...

Thank you Guenter - there's always something to learn with this product!

You could try making a view (in Access) of MSysObjects and attempt to access that?

--edit: (cough) Oops! I think they're just called 'queries' in Access 🙂

kevin.lanners (6/2/2009)

---

Thanks!

The update statement worked... I was right, it was pretty simple as soon as started thinking "outside the table"

Instead of referencing the newly created table I added an Execute...

Did you try my suggestion of changing the derived column's datatype to DT_STR?

Then we should be keeping DT_STR from one end of the pipeline to the other and your destination...

You just need to avoid mixing and matching your datatypes if you can. Working with DT_STR is just fine. Try using the Advanced Editor on your datasource and looking at...

Once again, I would suggest that the error message gives the game away. Try changing the data type of your derived column to [DT_STR].

Are you able to query user tables in the Access db?

Just wondering whether any additional permissions are required to query Access' system objects.

Or run a simple UPDATE query after the import has completed ...

You need to put a file there somehow for each of the connections you are creating.

Then create the connections, set 'delay validation' to true and delete the files.

greengiant (6/1/2009)

---

In the derived column name I left the text "derived column 1".

In the derived column I left "add a new column".

In the expression I added "@[User::xCurrStatus]" This is my...

Greg J (6/1/2009)

---

sorry Lynn. "UNION ALL" would have the desired effect in that example, but it seems too contrived to be elegant much less efficient.

Destination table has 150 columns.

There...

Does it have to be SSIS? Have you thought about using the Access upsizing wizard?