Problems with Linked FoxPro Tables

[wwmathieson]

I am using MS Access 2003 to preprocess tables from a FoxPro Application before using Crystal Reports for custom reports. I am getting inconsistent and erratic results - the data seems to always be right in my office, but when the client is running it in their office, sometimes it's right, sometimes it's wrong!

I've linked Access Tables to the related FoxPro Tables; created a blank table I call Dataset; using a macro, I run a series of Append Queries against the linked tables to populate the Dataset table.

This technique has worked fine in my controlled environment and occasionally in the client's busy office, but we can't tolerate the inconsistency! I've suspected that the FoxPro Data may be temporarily locked by other users, but the client has even tried refreshing the data at off hours when no one is in the FoxPro application (they think). I've shortened the refresh rates in Tools>Options>Advanced, but we're still not able to get consistently reliable data. Might it be that I should be importing the data, rather than linking? Any ideas would be greatly appreciated!

 

[wwmathieson]

In case anyone cares about this thread, I think I found the answer to the problem. When setting up the ODBC connection, I needed to uncheck the box found in the Advanced area so that it does not fetch data in the background. Now the data seems to be consistently correct.

Once again, a default value works against users that want accurate data!