Laurie, I went through this a while back. If you migrate to SQL Server 2005, it will work. SQL Server will automatically switch the database to 6.5 compatibility mode but you can flip it back when done. If you don't have a 2005 version lying around, you can download an Express version but the database has to be less than 4 GB. When your data is migrated, you can add it to your 2008R2 database server using a backup/restore.
Also, this upsizing code works much better than the FoxPro wizard: https://vfpx.codeplex.com/releases/view/10224. -----Original Message----- From: Laurie Alvey [mailto:[email protected]] Sent: Monday, February 09, 2015 4:01 AM To: ProFox Email List Subject: Re: VFP to SQL Server Migration Hi Dave, Thanks very much for your offer. I would like to be kept in the loop and your routines would be very helpful. Laurie On 9 February 2015 at 10:37, Dave Crozier <[email protected]> wrote: > Laurie.... you have only got one problem there...... i.e the Wizards!!! > > Tom, my new assistant currently has the task of writing a generic VFP > Table to SQL Server migrate procedure which SHOULD work on all VFP > Tables to any SQL/SqlExpress Server of any version (in our case 2008 and > 2012). > Progress is slow but sure at the moment as he is still getting to > grips with VFP but I am sure that it will be completed quite soon and > then we can add in bulk inserts/update transactions along with all the > other go-faster goodies for table that have lots of records and fields > in them > > We can always keep you in the loop if you still need to do it and are > struggling. I have these routines already in existence if you need > them right away but don't tell Tom!! ;-) > > Dave > > > -----Original Message----- > From: ProFox [mailto:[email protected]] On Behalf Of Laurie > Alvey > Sent: 09 February 2015 09:30 > To: ProFox Email List > Subject: VFP to SQL Server Migration > > Hi All, > > I'm trying to export a VFP9 database to SQL Server Express 2008R2. I > first tried the Upsizing Wizard from VFPX but it told me I had to set > the database compatibility level to 6.5 (no, that's not a typo, 6.5!). > The lowest the SQL instance will allow is 2000. > > I then tried the import/export wizard in SQL Server using the VFPOLEDB. > That failed as well, complaining it could not establish the code page > for the table columns. > > Short of manually creating the SQL Server objects and importing from > flat files, any ideas? > > Laurie > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
