Again, my source is the access table. The table may be linked to sharepoint, but it is indeed still an access table. I am not attempting to link directly to...

You are right. That is what I am doing it creating the new ssis package on the 64 bit server. I feel like we are so close.

If I try to...

This isn't a linked server, it is an access database linked to a sharepoint list.

That also doesn't make sense as to why it work on 32 but not 64.

What do you mean no security. No security where?

Just to add.....Why would i be able to query the new table on 64 and 32....but the linked table only on 32.

ok, so after reading another forum I created the new connection manager you said.

Steps:

Right click on Connection manager

New ADO.NET Connection

Chose .net Providers, ODBC Data Provider

Tested Connection "OK"

Created...

Ok, so I created the DSN, and then created the ODBC connection Manager.

I now need to add the data flow source, but I don't know which to use since...

See the attachment. Left is 32, right is 64.

I am unable to access blogspot at work...

I know how to use DTExec and I have ran the 32bit version. I got the same error. Runs fine on the 32...

Do you know where that location is?

ok. That makes sense, but how do I create an SSIS package on a 64 bit server and utilize 32 bit.

I don't think it is credentials. It works on 32 but not 64.

I am using access 2003. The DB is not password protected. The ssis package is password protected, but when i open it in BI it requires a password that I...

So i imported my task in to BI. I changed the project 64 thing to FALSE.

I clicked to debug and have this error on a perfectly fine package.

The error is...