Linking To FoxPro via ODBC problem

From: Salad (oil_at_vinegar.com)
Date: 06/28/04


Date: Mon, 28 Jun 2004 08:37:46 GMT

I have a problem.

My client has Win98 and AccessXp on a production PC....located on the
east coast.

I have WinXP, A97 and A2K installed on a Pentium 4 2gz, 1 meg
memory...located on the west coast, used for development. As near as I
can tell, WinXP comes with MDAC 2.7.

Initially, my XP machine had a Visual FoxPro driver version 1.00.02.00
dated 8/29/2002. Whenever I attemped to use this driver it told me to
go to MSDN and get the newest driver. I was sent to this site at MSDN
http://msdn.microsoft.com/vfoxpro/downloads/updates/odbc/default.aspx.

A97 can use the Isam FoxPro driver, A2K and above appears to require
ODBC. I downloaded FoxPro ODBC driver version 6.01.8269.01 from MSDN.
Both my client and I now have the same version. His driver date is
9/21/1999. Mine is dated 12/7/1999.

Can you tell what I am doing wrong? The following is how I set up the
ODBC dsn on my development PC after I downloaded the file from the above
link.

I get the ODBC administrator open. I click System DSN. I click Add. I
then select the VFP driver and click Finish. I enter Test for both
Data Services name and description. I select FreeTable, not DBC (VFP
can be a DBC or use dbf tables) and enter the path C:\Test as the path.
  I click Options; machine collate. The Null, Deleted, and Fetch data
in background (defaults) are checked. I click Finish. This is real quick.

I have a customer table with 167 records. I open up Access2000, click
File/GetExternalData/Link, select ODBC, select Test dsn. After about 5
seconds (slow) the tables in that directory appear. I select Customer.
  After 5-10 seconds it presents me with a list of fields that make the
unique index key. I select CustomerID and OK. I now have a link.

When I click on the customer table and press Open in A2K it takes about
1 minutes 15 seconds to open it. This is WAY TO LONG! I have
AutoCorrect set off in Access 2000 as I have read that also slows things
down.

I'm wondering at this point if I can even work on this application. On
my clients machine it is not as slow as mine. It takes about 5-10
seconds to open the customer file (167 records) and about the same to
open the orderlog file of 58K records. To open the Orderlog file on my
machine takes about 2 minutes.

If I open up the customer table the primary key is type decimal. What I
find intriguing is that ALL text fields are set to Required = Yes, Allow
zero length = Yes.

I imported the data instead of linked to it and pulling up the records
is instantaneous....as expected. I'm pulling my hair out on this
on...what little hair I have. If I use A97 and the ISAM driver, pulling
up the tables is instantaneous.

Any help will be appreciated.



Relevant Pages

  • Microsoft ODBC for Oracle Driver problem
    ... I think I have a resource issue with this driver. ... we are having an issue where suddenly the ODBC ... customer on that hosted machine. ... Microsoft ODBC Driver for Oracle. ...
    (microsoft.public.data.odbc)
  • Re: Printer Issues
    ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ... To troubleshoot I threw away all printers on the clients computer, ...
    (microsoft.public.windows.terminal_services)
  • Printer Issues
    ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ... To troubleshoot I threw away all printers on the clients computer, ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer Issues
    ... This had me quite surprised tho' as we have a whole bunch of customers ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer Issues
    ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ... To troubleshoot I threw away all printers on the clients computer, ...
    (microsoft.public.windows.terminal_services)