SOULUTION The parameter is incorrect. (Microsoft OLE DB Provider for Visual FoxPro) after SP1

SOULUTION The parameter is incorrect. (Microsoft OLE DB Provider for Visual FoxPro) after SP1

• Otto Fischer

  Using: (SQL Server Import and Export Wizard)

  1st Screen: Data Source: Micosoft OLE DB Provider for Visual FoxPro

  <Properties>
  1. Select or enter a database name: (Free table directory and then selecting Path:)
  "Test connection succeeded."

  2nd Screen: Destination: SQL Native Client
  Authenication: Windows Authenication (I am Systems Administrator)
  Database: the db name

  
  3rd Screen: Specify Table Copy or Query

  • Copy data from one or more tables or views. (Choose "Next>")

  This is where it blows up listing the tables:

  TITLE: SQL Server Import and Export Wizard
  ------------------------------

  The parameter is incorrect.

  ------------------------------
  ADDITIONAL INFORMATION:

  The parameter is incorrect. (Microsoft OLE DB Provider for Visual FoxPro)

  ------------------------------
  BUTTONS:

  OK
  ------------------------------

  Technical Details:

  ===================================

  The parameter is incorrect. (SQL Server Import and Export Wizard)

  ===================================

  The parameter is incorrect. (Microsoft OLE DB Provider for Visual FoxPro)

  ------------------------------
  Program Location:

  at System.Data.OleDb.OleDbConnectionInternal.GetSchemaRowset(Guid schema, Object[] restrictions)
  at System.Data.OleDb.OleDbConnection.GetOleDbSchemaTable(Guid schema, Object[] restrictions)
  at Microsoft.SqlServer.Dts.DtsWizard.OLEDBHelpers.GetDataTable(IDbConnection openedConnection, String tableType)
  at Microsoft.SqlServer.Dts.DtsWizard.OLEDBHelpers.LoadAllTables(IDbConnection myConnection, UpdateProgress updateProgressCallback)
  at Microsoft.SqlServer.Dts.DtsWizard.StepTablesStorage.InitializeForDataSource()
  

  
  

  
  

• Kay-Davis

  Not a dumb question...I did not specify. They said SP2 of SQL Server 2005 the fix should be in. Since it was only several months ago that SP1 was released, I fear that this may be several more months away before we get SP2. This is why I requested a hotfix but have gotten no response. I don't think they usually make hotfixes available unless enough customers complain about the issue...and judging from the posts on this subject, I don't think a lot of people are complaining :(

  Thanks,

  -David

  
  

• Niksta

  The workaround is to use ODBC for Foxpro. Unfortunately, it is a little cumbersome as invidual SQL statements must be used to retrieve the source data.
  

• Janta

  David Wilder wrote:

  I noticed at the Microsoft Connect link given in a previous post to this thread that this issue has now been corrected but it will not be available until Service Pack 2. Is there any way that we can get this as a Hotfix until SP2 is released Thanks, David

  all suggestions for sql server can be submitted here: SQL Server Feedback
  
  

• Cory.Isakson

  On my last post I incorrectly stated that the Microsoft forums they said they had fixed this and the fix would be available in SP2. I meant to say in the SQL Server Feedback discussion area they mentioned the fix and SP2.

  -David

  
  

• TkNeo

  This makes it definitely clear. Thanks.

  Would you please report the bug on the Product Feedback site (http://lab.msdn.microsoft.com/productfeedback/default.aspx) so we can investigate this and pass you the results of the investigation.

  In the meantime, I suggest you try to build the package in the designer without the wizard.

  I am sorry for the inconvenience.

  
  
  

• ewitkows

  Great, I just read on Bink.nu that SQL Server 2005 SP2 will not be released until Windows Vista goes RTM. Eight months for a fix since the time it was first broken...ridiculous.
  

• Nightmare_BE

  It is not clear how you use the FoxPro provider.

  Do you create packages manually or use the wizard Could you provide more detailed repro steps leading to the error you are seeing

  Thanks.

  
  
  

• Xcel

  Well on the Microsoft forums they say that this is fixed but it will not be available until SP2. I have posted a comment on these forums asking if we can get this as a hotfix so we don't have to wait until SP2, however I have received no response on this comment post.
  

• NateRickard

  Any update on this issue I urgently require this fix!
  

• Parag_Dave

  Dumb question - this will be fixed with SP2 for SQL Server 2005, or SP2 for VFP9 (or SP2 for Windows 2003 Server) LOL.

  
  

• Webbert

  I noticed at the Microsoft Connect link given in a previous post to this thread that this issue has now been corrected but it will not be available until Service Pack 2. Is there any way that we can get this as a Hotfix until SP2 is released

  Thanks,
  David

  
  

• Yudy

  I get the same problem as Tom, except that I use the .dbc database file as import source, not the free table directory. Is there anybody could solve this problem
  
  

• Lemon.oO0

  This is very frustrating, particularly since I have an import I made before installing SP1 that works okay, but can't add another using the wizard. It's going to be laborious doing all the tables manually. Shame one can't uninstall SP1...
  
  I doubt there will be any more service packs for FoxPro seeing as it's no longer flavour of the month. Given that these things invariably seem to fix a couple of problems, but create at least one more, I shan't fret.
  
  
• SOULUTION The parameter is incorrect. (Microsoft OLE DB Provider for Visual FoxPro) after SP1