(2) Again, I have the 32-bit version of the Microsoft Access Database Engine 2010 Redistributable installed on my development machine. Does this need to be changed to "True" before I build/deploy the solution for installation on my client's 64-bit SQL Server machine? (1) The "Run64BitRuntime" property for my SSIS solution in my 32-bit development environment is currently set as "False". I've read and read forum posts online about the 32-bit/64-bit situation with SSIS and am frankly very confused as to what (if any) changes/obstacles I need to be prepared for once I ultimately install the finished solution on my client's 64-bit SQL Server machine. The SSIS package will be called on the client's 64-bit machine via a SQL Server Agent job. It's your "standard" situation I guess as far as a machine that's intended solely to run SQL Server and doesn't have any extra stuff like Microsoft Office / etc. On the client's 64-bit SQL Server machine where the finished solution will ultimately be installed, the machine is *NOT* running Microsoft Office. Provider=.12.0 Data Source=C:\MyProject\ExcelFile.xlsx" Extended Properties="EXCEL 12.0 XML HDR=YES" My connection string used for my "Source" and "Destination" Excel Connection Managers is basically: I'm using the "Excel Connection Manager" to allow the package to connect to the numerous Microsoft Excel 2013 spreadsheets (.xlsx). On the development machine, I've installed the Microsoft Access Database Engine 2010 Redistributable (32-bit version). Most of the Excel spreadsheets are saved using the most recent version (MS Office 2013) of Excel. The main gist of the project is that the SSIS package will be looking for and accessing / manipulating a high volume of Excel spreadsheets nightly. Development is being done on a virtual machine (VMWare) that's a 32-bit environment. Obviously, doing so risks having our application not working, along with any other that uses MADE.I'm developing a comprehensive SSIS solution for a client. If there is a 32-bit version of MADE already installed (without MS Office on the computer) then I do not want to install the 64-bit MADE. My goal is to be able to run a check on the MADE (32 or 64-bit) to see if it is possible for the installation to continue. How can we determine what version of MADE that may already exist on their computer? Can we tell if it is 32-bit or 64-bit? I have done quite a bit of searching to see if I can find a way to determine which version of MADE is already installed, but have been unsuccessful to this point. Both 32 and 64-bit versions of MADE are now installed on the computer.In this scenario, a user could first install the 32-bit version of our application, uninstall and then install the 64-bit version. An issue arises when the user does not have MS Office installed. If a user uninstalls our application, the MADE is left untouched and remains on the user's computer.
The MADE install runs silently in the background. Depending on the version of MS Office installed, we then install the appropriate MADE (Microsoft Access Database Engine) version. We develop an application that installs on 32 and 64-bit machines.