>On the other other hand (lol) VFP connectivity with the rest of Office in OfficeXP is greatly enhanced via the new VFP OLE DB provider. I haven't tested the new Access yet, however, but I imagine with the OLE DB provider that will cease to be an issue as well.
>
>
At the risk of tarnishing my image by admitting I have a few Access apps out there, I'll say that from a programmer's perspective, Microsoft dropping FoxPro suuport from the Jet database engine was no big deal. When I need to connect to a Fox table, ODBC works. OLE DB will be better. It was a hassle for one project that stopped working when the linked tables dissappeared after they upgraded to Office 2000 (see MSKB Article# Q200393) but even that was a pretty quick fix.

My biggest pain was caused by the fact the Microsoft appeared to have dropped FoxPro support from Office2000, and this line from the KB article, Access to FoxPro data through the Microsoft Jet database engine is no longer supported. These were was used as fuel against me in the "Fox is going away" argument. An argument which, alas, I have lost, which is why I didn't see y'all in Orlando. :-(

On yet another hand, if I understand correctly, Access 2002 no longer supports the Access (Jet) database anymore either, only SQL and MSDE.