Installing a 32 bit application that uses 32 bit OLEDB drivers on Windows 7 64 bit with Office 2010 RRS feed

  • Question

  • I have a 32 bit application developed in VS2008 .NET/C sharp and currently running on Windows XP. The application reads and imports csv and xls files and currently uses the following connection strings to access the OLEDB drivers in order to read the files:

    Driver={{Microsoft Text Driver (*.txt; *.csv)}}

    The application is made up of a number of solutions, which are built using a TFSBuild.proj file with a CustomAction.targets file. In the Configuration Manager for each solution, the Active solution configuration is set to Debug and the Active solution platform is Any CPU. In the TFSBuild.proj file, the ConfigurationToBuild has FlavorToBuild set to Release and PlatformToBuild is Any CPU. 

    We also have a deployment project set up to create an .msi to deploy the project to the clients. Currently in the properties page for the project the TargetPlatform is set to x86. In the deployment project propeties - configuration manager the Active solution configuration is Release and the Active solution platform is Default.

    The clients are being upgraded to Windows 7 64-bit. What steps do I need to undertake in order to succesfully install and run the applciation in the new environment? We have had errors with Excel spreadsheets not working properly when they are opened, and when importing csv and xls file we get the following errors:

    "The Microsoft.Jet.OLEDB.4.0 provider is not registered on the local machine. "(when trying to read a csv file)

    “ERROR [IM002] [Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified” (when trying to read a xls file)

    From reading around, it looks like I need to specify the target platform as x86 so that the app will use the 32 bit OLEDB drivers. Where do I need to change this though, for every solution and the TeamBuild.proj file? And in the deployment project Configuration Manager? And what should the TargetPlatform be set to in the deployment project? Do I also need to change the connection strings to access the ACE OLEDB 12.0 and Microsoft Access Text Driver?

    Please could someone help to clarify what needs to be done?

    Many thanks

    Friday, May 10, 2013 6:02 PM