Import-Linking to FoxPro tables failes w/ "Invalid Argument"

  • Thread starter Thread starter mgannon
  • Start date Start date
M

mgannon

Am having a devil of a time with FoxPro to Access2002
import or linking. Error message of 'invalid argument'
appears about 90% of the time. If it was 100% I'd know it
was a fix-pak issue or something. I've got all of the
latest fixes and have deleted Access and/or FoxPro 8.0
and re-installed a half a dozen times. No Joy.

Is there any hope for me, or am I doomed to life of
frustation and sorrow?
 
I'm having the same problem in Access 2000. I want to
link or import VFP files to Access and I get an error
message that Access doesn't recognize the format. Is
there another import wizard that I can install as an
addin? Access import DBase files with the same
extensions. What's the problem?


Linda
 
I tried setting up a data source and linking the foxpro
file via ODBC connect. This works although when I had a
file with more than 300,000 records, it bombed.


Linda
 
Linda;

Thanks. Misery loves company.
I haven't noticed a size limitation, but I believe it has
something to do with the VFP file being "packed" or not.
The error "invalid argument" refers to an unstable state
in one or more columns. I've tried "packing" the file and
tried "saving as" and neither works regularly.

If anyone has a fix for our problems??? Please respond.

MGannon
 
Originally posted by Cindy Winegarden Microsoft Visual FoxPro MVP:

Start with the latest ODBC driver for FoxPro and Visual FoxPro, available
from
http://msdn.microsoft.com/vfoxpro/downloads/addons/odbc.asp. Download and
install it. (If you have trouble doing this, post back.)

You will need to determine whether you have FoxPro "free" tables or a
"database container" (contains metadata about the tables themselves). To do
this, navigate to your data directory and look for the presence of a DBC
file. If it's there you have a "database" otherwise you have free tables.

Now open up the ODBC dialog. In WinXP it's Start | Administrative Tools |
Data Sources (ODBC). Choose either the User DSN or the System DSN. (The
difference lies in whether you want other people to be able to see it if
they use your machine.)

Click Add... Scroll down to the Microsoft Visual FoxPro Driver. Scroll over
to verify that it's version 6.01.8629.01. Click Finish.

Now you're at the ODBC Visual FoxPr Setup dialog. In the first box (Data
Source Name) enter a friendly name that you will use to recognise this data
source - My FoxPro Data Source. You can add more text in the description
box.

Below are two options. Choose Visual FoxPro database (.DBC) or Free Table
Directory - whichever you have determined is correct.

Browse to locate your directory, or your specific DBC file.

You can click the Options>> button for more choices. The defaults should be
ok. "Exclusive" refers to whether you want to have exclusive access to the
data while you're using it. "Null" allows you to enter Null values or not.
Older FoxPro tables do not allow Nulls. "Deleted" means to hide deleted
records. This one's important if you are working with primary keys - more in
a minute. "Fetch data in background" will allow you to see the first few
lines of a large tablel while the rest is being retrieved. You can also
indicate a collating sequence if you're using a non-English alphabet.

Click OK and you're done.

Now, about deleted records. When a record is deleted in a FoxPro or Visual
FoxPro table it's merely marked as deleted and filtered out, but is still
physically present in the table. If you have a unique index and you delete
the record with a key value of 123 you can not enter another record with
this value, even though you can't see the record. To get rid of records
entirely, you must issue a PACK command. However, the best rule to follow is
to not reuse primary keys.
 
Back
Top