The actual error message:

Msg 105082, Level 16, State 1, Line 21

105082;Generic ODBC error: NativeOdbcConnection.Open, error in OdbcConnectionCreate: SqlState: 08004, NativeError: 1, 'Error calling: SQLDriverConnect(this->_hdbc, NULL, (SQLWCHAR*)connectionString, SQL_NTS, NULL, 0, &cbConnStrOut,...

I have 3 seperate DSN's on the SQL server instance , each pointing to a database on the BBj server. So I would have expected to point to the DSN...

I guess you haven't met our customers. This is  Microsoft Visual Basic 2010 and i'm stuck with it.

Passing the parameter is the cause of the delay it seems. Hard-coding provides...

I tried incorporating Jeffrey's suggestion, but the ancient VS version I have to work with keeps crashing in the expression builder.

So, I decided to use the hardcoded solution and some...

@ Jeffrey Williams:

Yes, I responded to your input and I answered Jeff Moden in the same post.

Sorry, if that caused confusion.

All solutions work from a technical perspective, but passing the...

Well, hardcoding would be an option, though this would require some maintenance issues if customers decides to need to look further into the past.

The source system is an Axapta ERP...

select

a.dataareaid

,a.ledgerdimension

,a.inventtranspostingtype

,a.inventtransorigin

,a.voucher

,a.transdate

from

Inventtransposting a

where a.transdate >= ?

transdate is a datetime type

Adding  the  option (recompile) slows it down even further , taking an additional 30 seconds to start the dataflow

Customer rebuild the .dsv and query expression within the model. Redeployed and the problem appeared to be solved.

Thank you for this extensive reply.  I think it does make a lot of sense.

Next friday I'm going to test through VPN to the clients server.

The really weird thing is ...

Well, in this case customers are upgrading and expect old solutions to migrate seamlessly. We are trying to make the best of it  🙂

You are absolutely right. However, the missing DLL's are part of the MSFT 2008R2 operating system, which means that our predecessor never evaluated the chance future operating systems might work...

I took the following approach:

1. Downloaded and installed VS2015  Community Edition.
2. Opened copy of solution (with all components in folder solution)
3. Message about not being able this type of project.

...

Well sidebar or not, we live in a world crowded with legacy solutions inherited. My team inherited everthing developed based on SSIS from way back when. As much as I...

I just checked. The rights on the specific package that is causing trouble is identical for all other packages for the user defined for SQL server Agent.