October 1, 2007 at 10:02 pm
Hi,help needed in migrating clipper to sql.what are the steps,things to know..thanks!
October 1, 2007 at 10:07 pm
from what i remember Clipper was just a Visual Foxpro, right? so it's simply a .DBF file you connect to using dts and import the whole thing:
Enterprise Manager, Select database...Right Click...All Tasks...Import Data.
select a foxpro driver,maybe maybe have to create a file dsn to point it at the dbf and click next 5 times.
Lowell
October 2, 2007 at 10:55 pm
Clipper!, what version? Most likely you'll need a driver that supports old dBaseIII/IV files or Foxpro 2.6/2.8 files. Newer versions of Foxpro will read the old files natively but I don't know if the current ODBC drivers will go that far back.
October 7, 2007 at 9:15 pm
Clipped should be Fox 2.x or dBase IV if I remember. I'd think that any DBase driver would read it.
Use the Import Wizard in SQL Enterprise Manager and try some of the Fox or dBase driver selections.
October 16, 2007 at 1:42 pm
If I remember correctly, Clipper was originally straight dBase III files (dbf) with their own souped up indexes (idx? instead of ndx). There may have been a version of Clipper that was dBase IV compatible. I have linked to old dBase III dbf files using MS-Access and been able to put the data out that way.
Steve
October 16, 2007 at 1:56 pm
Man - it really throws me back to read the "old style" Clipper ads (believe it or not - Clipper is STILL BEING SOLD. CA sold it off to an outfit called GrafXsoftware).
Here's the ad with what sounds like the original feature list. Gotta love features like:
- has a Full graphical mode
- is fully mouse-compatible
- Protected mode
- Integration with Microsoft C (not Visual C, not C++, not C#....C)
let's just say...wow!
Here's the link: http://www.grafxsoft.com/clipper.htm
Clipper was a DBase 3+ format dialect, so I don't think you need to worry too much. One thing you MIGHT acre to pay attention to is whether the date fields convert to the same values: some DBASE clones assumed 0 was a different date than 1/1/1900, just like Access used to, so you might need to run a "increment all of the converted date fields by some amount".
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy