September 5, 2008 at 10:29 am
I've been retrieving data from Foxpro .DBFs using Linked Servers (using the Microsoft OLD DB Provider for ODBC) in Stored Procedures with SQL Server 2000. Now I want to got to 64bit SQL Server 2005. I've found that the Foxpro ODBC and OLD DB drivers are 32-bit and reportedly can't be used in the 64-bit environment.
What are my options to continue to retrieve Foxpro data within stored procedures in 64bit SQL Server 2005?
Thanks for any suggestions
September 5, 2008 at 10:59 am
The only thing I can think of is set up an intermediate server with 32-bit. Maybe an instance on the same server. That might work, but it seems like overkill even if it does work.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
September 5, 2008 at 11:41 am
I have to agree with GSquared, unless you feel up to writing your own OLE DB driver... Perhaps the larger issue is the TRUE cost of continuing to support an ancient database format. Somehow I have trouble imagining an application old enough to use FoxPro .DBF files, yet so complex that it simply couldn't be duplicated in MS Access with the tables on SQL Server. Even if you have to build it from scratch, the benefits of doing so might well far exceed the temporary cost of conversion plus all the costs of continuing to support ancient history.
Steve
(aka smunson)
:):):)
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
September 5, 2008 at 4:11 pm
It's sure sounding like the best way to go is to convert the few tables that we're accessing via linked servers to SQL Server and be done with it.
Thanks for the comments.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply