To move the data into sql server, you likely don't want, or need to use
ms-access.
once you get the data into sql server, then you can consider linking tables
to an MS access application, but for the most part the Moving of data to SQL
server is a separate issue, and no one except the two separate issues here.
MS access is likely not the tool to use to import the data SQL server. as
for keeping index information intact, because the architectures and indexing
systems are so fundamentally different, it is of little use to attempt to
worry about that issue at all, it is a complete waste of time on your part.
I would consider asking your question in SQL newsgroup as to how import the
data from Foxpro into SQL server, don't waste your time using MS access as
an intermediate system unless there's some particular issue as to why you
must or need to do this.
You can use MS access to import the data, and then you could use the
upsizing wizard in MS access to move the data up to SQL server. so you could
consider at least linking to the Foxpro tables, or importing the Foxpro data
into MS access.
if you're looking as to how to use the ODBC driver, and linked tables to
Foxpro, here's some info:
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.
(the above seems wrong now..try the following <nb: Albert K.>
http://msdn.microsoft.com/vfoxpro/downloads/updates/odbc/default.aspx
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.
