locked
Migrate FoxPro DB to Sql Server RRS feed

  • Question

  • I want to migrate a FoxPro DBC database to SQL Server, does anybody has any strategy document?
    Does SQl Server has any wizard to do it?
    Monday, February 15, 2010 9:31 PM

Answers

All replies

  • I want to migrate a VFP database to SQL Server
    • Edited by GabyGonz Thursday, February 18, 2010 7:55 PM
    • Merged by Martin_Xie Friday, February 19, 2010 3:49 AM Merge them to keep in one same topic.
    Monday, February 15, 2010 9:28 PM
  • Check below documenation. It will be helpful to you..

    http://nationalcom.com/home/download/Conversion-VFP-SQLServer.pdf






    Please "Mark as Answer" if this post answered your question. :)

    Kalpesh Chhatrala | Software Developer | Rajkot | India

    Kalpesh's Blog
    • Marked as answer by Martin_Xie Monday, February 22, 2010 5:33 AM
    Tuesday, February 16, 2010 4:38 AM
    Answerer
  • SQL server has integration services (SSIS) and export/import wizard. VFP have upsizing wizard. Also there are other ways like using linkedserver, bulk copy etc It is easy to write your own.
    • Marked as answer by Martin_Xie Monday, February 22, 2010 5:33 AM
    Tuesday, February 16, 2010 12:00 PM
  • Hi GabyGonz,

    Welcome to MSDN forums!

    Actually you can import FoxPro database to MS Access database via Office Access IDE Wizard.

    In Office Access 2007/2003, you may not be able to directly import FoxPro databases because the Import dialog boxes do not include the FoxPro database as an option in the Files of type list.

    This problem occurs because the Microsoft FoxPro ISAM driver is not included in Access 2007 and in Access 2003.

    How to Import from a FoxPro database to MS Access database

    To import data from a FoxPro database, use the Microsoft Visual FoxPro ODBC driver. To do so, follow these steps:

    1.   Click Start, and then click Control Panel.

    2.   In Control Panel, double-click Administrative Tools.

    3.   In the Administrative Tools window, double-click Data Sources (ODBC), and then add a new ODBC data source for your FoxPro database or tables by selecting the appropriate Visual FoxPro driver.

    4.   Start Access, and then open your Access database.

    5.   On the File menu, point to Get External Data, and then click Import.

    Note If you use Access 2007, click More in the Import group on the External Data tab, and then select ODBC Database.

    6.   In the Import dialog box, click ODBC Databases in the Files of type list.

    Note If you use Access 2007, click to select the Import the source data into a new table in the current database option in the Select the source and destination of the data dialog box, and then click OK.

    7.   In the Select Data Source dialog box, click the Visual FoxPro data source that you created in step 3, and then click OK.

    8.   In the Import Objects dialog box, click the tables that you want to link, and then click OK.

     

     

    Please check this KB article for details:
    http://support.microsoft.com/default.aspx/kb/824264

     

     

    Best regards,
    Martin Xie


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

    Wednesday, February 17, 2010 2:32 AM
  • Don't use the upsizing wizard that ships with VFP. Use the all new one at http://vfpx.codeplex.com
    Craig Berntson
    MCSD, Visual FoxPro MVP
    INETA Regional Speaker
    www.craigberntson.com
    Thursday, February 18, 2010 5:09 PM
  • Wow.. why would you want to do this? Access (or more technically correct, Jet) databases have more problems than VFP. They are:

    - more suspectible to corruption. In fact, because forms are reports are stored in the same database, you can lose the entire app.
    - are slower
    - support fewer users
    - have smaller capacities
    Craig Berntson
    MCSD, Visual FoxPro MVP
    INETA Regional Speaker
    www.craigberntson.com
    Thursday, February 18, 2010 5:12 PM
  • Sorry , I want to migrate VFP 6 tio SQL Server not to Access.
    I´m trying ti get information for a friend of mine who works in an  enterprise that have an application built in VFP 6.
    Thery consider necessary to migrate to any DB more powerful.
    Could you pls give information about VFP 6 limitations?
    Thursday, February 18, 2010 7:39 PM
  • It really depends on what they consider "more powerful".

    SQL Server generates less network traffic, is easier to backup, has much bigger capacity, better security, etc, but it is not necessarily faster.

    And it isn't as simple as moving the data. Depending on how the VFP application was written, it could require a complete rewrite to move to SQL Server or be as easy as creating Remote Views instead of Local Views.
    Craig Berntson
    MCSD, Visual FoxPro MVP
    INETA Regional Speaker
    www.craigberntson.com
    Monday, February 22, 2010 3:22 PM
  • I want to migrate a FoxPro DBC database to SQL Server, does anybody has any strategy document?
    Does SQl Server has any wizard to do it?
    Take a look at the tool from DBConvert at http://www.dbconvert.com/convert-foxpro-to-mssql-pro.php?DB=7
    Friday, February 26, 2010 12:52 AM
  • Hi Kalpesh
    Thanks for the response.
    A little more details about my problem.
    A friend of mine has a shop. He works with an application build in VFP6.
    The DB has (9.75 GB) and a year growth of 2.5 GB per year.
    Do you think it is necesarry to migrate to SQL Server?
    Tuesday, March 9, 2010 5:25 PM
  • Hi Kalpesh
    Thanks for the response.
    A little more details about my problem.
    A friend of mine has a shop. He works with an application build in VFP6.
    The DB has (9.75 GB) and a year growth of 2.5 GB per year.
    Do you think it is necesarry to migrate to SQL Server?
    Necessary? No. 
    Might be a good option? Maybe. Depends.
    Tuesday, March 9, 2010 8:52 PM