I am able to "Get External Data" using OLEDB provider for Visual FoxPro in Excel 2002 but what I need is to do that from Access.

But Access only shows native or ODBC connections for Linking or Importing tables.

I cannot use the ODBC driver for Visual FoxPro since it does not return correct results. In this regard, I was told that the latest ODBC driver for FoxPro only support up to version 6 and we're using version 9.0.

Any help would greatly be appreciated.

Djinn

Can you use Provider statements instead of an ODBC connection? Like:

Like

Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\Northwind.mdb;User ID=Admin;Password=???;

Also, take a look at MSDN.

Did that help any?


mmcdonal

The problem with using such code is that it requires opening the .mdb and running an app, at least I think.

What I'm trying to do is the following.

We have a project management Foxpro application that stores data in 6 separate folders (free tables). We need a program wide report that combines the 6 projects.

I'm using Crystal for reporting. I started by simply linking the FoxPro tables in MS Access then created a union query that combined the various project tables together. That scenario never require the user to open the Access database, just running the Crystal report. Access is just used as a go-between.

Everything worked fine until I noticed that Access returned different results on every run.

What I would like is to be able to link to the FoxPro tables via OLEDB just as I was linking via ODBC. This mechanism is available in Excel as well as in Word. Why in the world is it not available in Access?



Djinn