Just Googling - does this help: http://dbconvert.com/convert-foxpro-to-mssql-sync.php



>I'd like to be able to back up a VFP database ( i.e. DBC and associated tables ) even if one or more users are actively working with it. Preferably using VFP code, but I'm open to other techniques ( e.g. LLFF ) if necessary. I'd like to avoid 3rd-party applications if possible.
>
>The database nor its tables are not currently used EXCLUSIVEly by anyone, so SHARED access should always be available. However, momentary locks will occur during backups and will need to be avoided or handled as necessary.
>
>With free tables, it looks like COPY TO or SELECT should easily do the job. But, a DBC and its tables looks more difficult. My first thought:
>
>- open the DBC SHARED, as a table
>- use COPY TO ( WITH PRODUCTION ) to create a copy in another folder
>
>I see Cetin has FAQ#7694 with some code that supposedly addresses this in a different way, I haven't looked at that yet.
>
>But, now it looks like a chicken-and-egg situation:
>
>- if I open the new DBC and its member tables are not present, does VFP check for that and cause an error?
>- if I open up member tables in the source, and COPY TO ( target ) DATABASE BackupDBC, does that create another reference in the DBC to a new member table, even though the reference is already there in the copied DBC file?
>
>It seems to be an issue of somehow handling the backlinks.
>
>Anyone have any experience with this?