> Another option is to use the Microsoft ADO driver directly through the > ADO components for Foxpro/dbase etc. > > The microsoft drivers aren't so bad. and it means that you always know > who you can blame if it doesn't work. The Microsoft Drivers are bound > to be the best drivers for using microsoft foxpro tables. > > Then you won't need the BDE at all, and you already have the TADO components. > > Regards > > David > _______________________________________________ >
This is Microsoft at it's Best! Just did a search for "Visual FoxPro ODBC Driver" and I did find it. It requires MDAC 2.6 and it shouldn't be installed if the system already has MDAC 2.5 (yes, the lower version). Naturally, there's an installer for WinMe and an installer for WinNT (I assume the "NT" installer works for XP). If I decide to use the VFP ODBC Driver I'll need to include both versions in my installer package (both "NT" version and "9x" version). Next I'll need to include MDAC 2.6 (or whatever's latest), just in case the system doesn't have it. With a bit of luck I'll need to include 2 versions of the MDAC, one for Win Me one for Xp/NT. Back to basics. The VFP ODBC driver for NT alone is a 5,9 Mb file. I assume the 9x one is about the same size. The installer for my application is around 3Mb at the moment, and my preferred channel of distribution is the Internet. I don't like the idea of adding an extra 12Mb of stuff to my 3Mb setup.exe just to gain the ability to export into Visual Fox Pro format. This is plain stupid, and now I remember why I'm not using Ms SQL: you pretty much need a CD to deploy, you can't deploy over the Internet. Who knows, tomorrow we'll be distributing our software on Blue Ray disks, so we have room for everything Microsoft. Thanks, Cosmin Prund _______________________________________________ Delphi-DB mailing list Delphi-DB@elists.org http://www.elists.org/mailman/listinfo/delphi-db
