Hello Everyone, I don't know if this is the right place for this question, but please feel free to move me to wherever is most appropriate. I'm having problems getting the Visual FoxPro 9 OLEDB Data provider to work. When I install it, I get no errors, and it shows up in the SQL Server Import and Export wizard. However when I try to use it (either through clicking on the Properties button or hitting next) it gives me the error posted below and completely locks up. I have tried installing and uninstalling multiple times. Different versions of SQL Server: 2008 R2 Developer and 2008 R2 Standard both to no avail. both have been fully updated along with the operating system. I have been fighting with this for a number of days now, and any help would be greatly appreciated. --Charly Machine Specs: Windows 7 Professional x64 AMD Athlon II X4 635 Processor 2.90 GHz RAM 6.00 GB =================================== An error occurred which the SQL Server Integration Services Wizard was not prepared to handle. (SQL Server Import and Export Wizard) =================================== External component has thrown an exception. (Interop.MSDASC) ------------------------------ Program Location: at MSDASC.DataLinksClass.PromptEdit(Object& ppADOConnection) at Microsoft.SqlServer.Dts.DtsWizard.OLEDBForm.buttonProperties_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

You may need to run SSIS in 32 bit mode. See http://msdn.microsoft.com/en-us/library/ms141766.aspx. A similar problem occurs when using Excel connection managers on a 64 bit machine (http://sqlblog.com/blogs/andy_leonard/archive/2010/01/19/ssis-snack-ssis-excel-and-a-64-bit-os.aspx). Russ Loski

Almost certainly a 32 bit driver issue. Old stuff like FoxPro is highly unlikely to have a 64 bit driver written for it.James Beresford @ http://www.bimonkey.com SSIS / MSBI Consultant in Sydney, Australia ##### BI Monkey SSIS ETL Framework @ http://ssisetlframework.codeplex.com/

Not sure there is an answer here. While Windows Server 2008 R2 is installed as 64-bit; SQL Server 2008 R2 was explicitly installed in 32-bit mode to support Visual FoxPro. However; when running the SQL Server Import and Export Wizard (32-bit), selecting the Properties button with the Microsoft OLE DB Provider for Visual FoxPro throws and exception. "External component has thrown an exception. (Interop.MSDASC)" I have installed the OLE Driver from Microsoft Visual Foxpro Site; to enable Foxpro drivers on this server. To further debug this; I installed the SQL components on my Vista x32 system; and the SQL Server Import and Export Wizard still throws an exception, but the problem does present itself slightly differently. On my client PC I see the dialogue box for the file locations present; and then it goes away and a large window with alot of text is displayed. "System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt." What I do know is that I have successfully used the OLE DB Provider in SQL Server to establish a Linked Server; and have been reading the tables without error; so the OLE driver is functioning properly on the SQL Server.Directory of Technology