If you have connected to FoxPro tables via ODBC, please read/help

[Salad]

I am having a problem with linking to FoxPro DOS tables in Access2000.
Simply opening the tables are EXTREMELY slow. Let me tell you how make
my connections to these tables. I could easily be doing something
wrong. I have a 2.6 gz machine, 1 gig memory, lots of disk space,
Access2000 has sp3 installed.

I get the ODBC administrator open. I click System DSN (or UserDSN if I
want to test it that way). 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 database
container or use dbf tables). I 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 dbf tables in C:\Test 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. It takes another 15 seconds after
presenting the records before Access gives me back the cursor. I have
AutoCorrect set off. Opening the Orderlog table, with 58K records,
takes about 2 minutes to display the records and about 30 seconds after
that it gives me back the cursor so I can scroll the records. It's like
the tables are 1 big calculated table.

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 1-3
seconds to open the customer file and maybe 5-10 to open the orderlog
file. His OS is Win98.

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 have no idea why all fields are set to be required
as I'm sure some fields are blank.

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.

Can you see anything that I am doing wrong? Any opinions?

[Michael Hopwood]

It could be your ODBC driver, check which version your friend is using
against yours.

--
Michael Hopwood
"Salad" <oi*@vinegar.com> wrote in message
news:K1******************@newsread2.news.pas.earth link.net...

I am having a problem with linking to FoxPro DOS tables in Access2000.
Simply opening the tables are EXTREMELY slow. Let me tell you how make
my connections to these tables. I could easily be doing something
wrong. I have a 2.6 gz machine, 1 gig memory, lots of disk space,
Access2000 has sp3 installed.

I get the ODBC administrator open. I click System DSN (or UserDSN if I
want to test it that way). 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 database
container or use dbf tables). I 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 dbf tables in C:\Test 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. It takes another 15 seconds after
presenting the records before Access gives me back the cursor. I have
AutoCorrect set off. Opening the Orderlog table, with 58K records,
takes about 2 minutes to display the records and about 30 seconds after
that it gives me back the cursor so I can scroll the records. It's like
the tables are 1 big calculated table.

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 1-3
seconds to open the customer file and maybe 5-10 to open the orderlog
file. His OS is Win98.

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 have no idea why all fields are set to be required
as I'm sure some fields are blank.

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.

Can you see anything that I am doing wrong? Any opinions?

[Salad]

Michael Hopwood wrote:

It could be your ODBC driver, check which version your friend is using
against yours.
Same drive as mine but with a different date. His is 9/21/1999, mine is
12/7/1999. I think I may ask him to buy A97 instead and forego the
newer MS bloatware.


--
Michael Hopwood
"Salad" <oi*@vinegar.com> wrote in message
news:K1******************@newsread2.news.pas.earth link.net...

I am having a problem with linking to FoxPro DOS tables in Access2000.
Simply opening the tables are EXTREMELY slow. Let me tell you how make
my connections to these tables. I could easily be doing something
wrong. I have a 2.6 gz machine, 1 gig memory, lots of disk space,
Access2000 has sp3 installed.

I get the ODBC administrator open. I click System DSN (or UserDSN if I
want to test it that way). 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 database
container or use dbf tables). I 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 dbf tables in C:\Test 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. It takes another 15 seconds after
presenting the records before Access gives me back the cursor. I have
AutoCorrect set off. Opening the Orderlog table, with 58K records,
takes about 2 minutes to display the records and about 30 seconds after
that it gives me back the cursor so I can scroll the records. It's like
the tables are 1 big calculated table.

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 1-3
seconds to open the customer file and maybe 5-10 to open the orderlog
file. His OS is Win98.

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 have no idea why all fields are set to be required
as I'm sure some fields are blank.

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.

Can you see anything that I am doing wrong? Any opinions?