WayneS (4/28/2010)
Ian Yates (4/28/2010)
Now if only they'd do one for FoxPro....... 🙂 (we link to a number of third party systems that use FoxPro databases)You do know that a FoxPro dbf is just a flat file with a header? It's been a decade since I've worked with it, but I remember the company having problems exporting data from a mainframe computer into a FoxPro dbf, and having issues. We ended up exporting it into a flat file, and appending the header.
So, if you can strip off the header, you can then just do a bulk import...
If only life were that simple 😛 Thanks for the suggestion, but we need to read from several tables at the same time, usually picking out just a couple of records (there's a trigger initiated by the user which tells us which record to examine) and bog standard SQL queries are easier to debug. I don't want to have to parse the index files, the blob files (*.fpt I think), etc to read out different bits of data.
We also do frequent full imports as well so your approach could work there, but I'd probably just use SSIS in that case if linked servers weren't available.
Someone had suggested that the Sybase Advantage Anywhere driver could read FoxPro files. It seems that it can, but it isn't x64 either and I never got it to work anyway.